Skip to main content

Managing Model Access

Approving Access Requests​

Users can request access to models directly from the AI Catalog. When they do, a request appears in the Admin → Model Access panel under the Access Requests section.

Steps​

  1. Open Admin → Model Access in the sidebar
  2. Under Access Requests, find pending requests (highlighted in yellow)
  3. Click Approve to grant access, or Deny to reject it

When you approve a request, the user immediately gains access and their model will turn green in the catalog.

Resolved requests (approved or denied) are shown in a collapsible section below for reference.

Manually Granting or Revoking Access​

You can also manage access directly without going through the request flow.

Prerequisites​

  • You are logged in with an account in the platform-admins group
  • The user has already generated an API key (they must do this first to appear in the table)
tip

If a user is not listed in the Consumer Access table, they have not generated an API key yet. Ask them to go to Developer → API Keys and generate one first.

Steps​

  1. Open Admin → Model Access
  2. In the Consumer Access table, find the user by username
  3. Check or uncheck models to grant or revoke access
  4. Click Save on the row

Changes take effect immediately.

Revoking Access​

To revoke a user's access to a model, uncheck it in the Consumer Access table and save. The user's requests to that model will immediately start returning an error.

Troubleshooting​

User not appearing in the admin panel​

The user must have generated an API key first. Ask them to go to Developer → API Keys and generate one.

Model not appearing in the admin panel​

Models are discovered automatically from the platform configuration. If a model is missing, contact a platform engineer to verify the model route is correctly configured.

Access granted but user still cannot use the model​

  1. Ask the user to refresh their AI Catalog page
  2. Verify the user is using the correct API key (from Developer → API Keys)
  3. Make sure they are sending requests to the correct endpoint shown in the catalog