Skip to content

Model Access Control

Admin Controls includes policy management for model access and generation blocking behavior.

Each Admin Controls section has a consistent header with a collapse control, so admins can keep dense policy, request, and audit panels open only when needed.

Policies can be scoped to:

  • Global
  • User
  • Team

Policies can target:

  • All models
  • A specific model

A policy can act as:

  • Immediate hard block
  • Threshold-based block using monthly USD limits
  • Monitor-only behavior (when configured without active blocking)
  1. Open Admin Controls.
  2. Choose scope type and scope target.
  3. Choose model target.
  4. Set optional monthly threshold.
  5. Configure denial message if needed.
  6. Enable enforcement and save.

Admin Controls includes policy logs and request history views for operational traceability.

Use this playbook for repeatable administration:

  • Review metrics and policy thresholds on a regular schedule.
  • Apply the smallest viable permission or policy change first, then observe impact.
  • Communicate policy changes to affected teams before enforcement windows.

If governance controls are not behaving as expected:

  • Confirm scope (global vs team vs user) and precedence rules.
  • Validate that users are assigned to the correct teams and role groups.
  • Re-check policy thresholds and effective dates when behavior appears delayed.

Why are users still blocked after a policy change?

Section titled “Why are users still blocked after a policy change?”

They may be affected by a stricter scope layer or stale session context.

Use role-based defaults and grant temporary exceptions with explicit review dates.

Spend trends, failure rates, exception volume, and policy-threshold pressure by team.