Restrict model/provider access
Add a model or provider deny rule, confirm its saved scope, and verify the affected request path.
Deny a model, a provider or their exact combination for an organization, Team or Member, then verify the affected request path.
Before you begin
Required
- Organization Admin access
Use the organization's Admin role.
- Live management records
Sample records do not permit writes.
- A matching active deny can refuse a supported request with HTTP 403.
- With no matching deny, admission is allowed by default.
- There is no separate allow-rule creation flow in the current console.
- Budgets and rate limits remain separate admission controls.
- Provider availability, model mappings and routing preferences are separate from deny rules.
Check model availability
A model needs an enabled provider connection and a valid model-to-provider mapping. For a missing model, check the organization's provider connection and pricing-sheet mapping before changing access rules. Admission still depends on other matching controls.
Add a deny rule
- Open Security → Access rules and select Add deny rule.
- Choose Organization, Team or Member under Scope. For Team or Member, select the subject from the organization directory; use Teams and hierarchy to confirm membership.
- Enter an exact model ID, select a provider, or set both filters. At least one filter is required. When both are set, the request must match both.
- Select Add deny rule to save an active deny.
- Confirm the saved scope, filters and active status in the refreshed list.
- The form and first list row select the same organization, provider and model.
- This combination matches
grok-4on Grok (xAI). It does not deny every model on that provider.
Check the result
- Test a new request through the intended supported path after configuration delivery.
- Compare its status, model, provider and time with the matching resource in Recent denials, when available.
- An HTTP 403 response is refusal evidence. The saved active row alone does not establish application.
- A Member rule selects one directory person.
- A Team rule selects a Team, including its actual membership.
- A member shown in an org chart is not automatically within that Team scope.
Allow access again
- Find the active deny matching the intended scope, provider and exact model.
- Select Disable on that row and confirm the action.
- Confirm that the retained row shows Disabled in the refreshed list.
- Review other matching Organization, Team and Member rules. Other active matching rules can still refuse the request.
- Test a new request after the configuration reaches the affected path. Successful admission still depends on credentials, rate limits and budgets.
Disabling one deny restores default allow only when no other active deny matches. It does not create an allow override. The opening list shows active and disabled records together.
Troubleshooting
| Symptom | Next action |
|---|---|
| Add deny rule is disabled | Confirm Admin access and that the page has live records. |
| The form cannot save | Select a resolved directory subject when needed and provide at least one model or provider filter. |
| The rule covers too much or too little | Review the exact model ID and provider. Both filters must match when both are set. |
| HTTP 403 persists after disabling | Review other active matching denies and the affected path's configuration delivery. |
| The request returns HTTP 402 or 429 | Inspect the budget or rate-limit resource in Troubleshoot refusals. |
Routing is a separate control
- Smart Router's allowed-model list restricts replacement targets.
- An incompatible replacement can preserve the original model, so that list is not an admission fence around the original request.
- Use access rules for model/provider admission requirements. See Understand routing decisions for routing evidence.