Skip to main content

Model policies

Model policies control primary-model availability for users, departments, and user groups.

Model policies control primary-model availability for users, departments, and user groups. Allowlists grant access and blocklists deny access. A blocklist takes precedence when both match the same member. BYOK (bring your own key) is available according to the capabilities enabled for your enterprise. Credits and limits in this guide refer to QwenWork credits. Check external model usage and charges on the model provider’s platform.

Create an allow or block policy

  1. Open AI → Models → Model policies and add a policy group.
  2. Enter its name and choose allowlist or blocklist.
  3. Select all users or specified users, departments, or groups, then check the selected scope.
  4. Select primary models. All models includes models added in the future. Select specific models when only reviewed models should be available.
  5. Check client targets and the impact message, save, and verify that the policy is enabled.
Admin console: select a user scope and model scope.

Adjust the default policy

The default allow policy is always enabled and cannot be deleted. You can edit its permitted model set. Before adding a pilot allowlist, also check the default policy so it does not continue exposing the same model to other members.

Verify a member's available models

  1. Open match verification and choose a member.
  2. Inspect matched policies and the final rules, then open those policies to check their selected models.
  3. Verify a member outside the intended scope to check that access has not expanded.
  4. Have the test member open the client's model selector and check available options.
Disabling or deleting a policy causes availability to be evaluated against the remaining enabled policies. The model remains in Catalog; remove it there when needed. Return to: Models overview