Skip to main content
Resource restrictions let you keep a sensitive project, dashboard, or prompt in a shared space without opening it to everyone there. A restricted resource is visible only to the people you add and to space, organization, and account admins, who keep access without a binding. Only generative (LLM tracing) projects can be restricted, and only a Space Admin or above can restrict a resource or manage its access list.

Restrict a project

  1. Open the project, select the three-dot menu, and choose Config.
  2. Under Access Control, set Visibility to Restricted.
Project visibility dropdown with Unrestricted and Restricted options
Add each person who needs access and give them a project role. Space members without a binding lose access immediately. Setting the project back to Unrestricted restores space-level access and keeps the bindings for the next restriction.

Restrict a dashboard

The dashboard’s access settings control who can see it. Everyone in this space follows each member’s space permissions. The restricted option limits the dashboard to the people you add.
Manage access dialog for a dashboard with a who-can-access setting and a list of people with access
Dashboards have no managed roles and POST /v2/role-bindings accepts only SPACE and PROJECT, so a restricted dashboard is open only to space, organization, and account admins.

Restrict a prompt

  1. In Prompt Hub, open the prompt’s row actions and select Manage Access.
  2. Choose the restricted option.
  3. Add the people who need access and save.
Manage access dialog for a prompt with a who-can-access setting and a list of people with access

Project roles

Restricted projects use three managed roles.
  • Project Viewer reads spans and eval tasks.
  • Project Editor also annotates spans and manages eval tasks.
  • Project Admin has full access, including create and delete.
A custom role can be bound instead. API keys respect restrictions: a call against a restricted project needs a user with a binding or an admin. A SAML role mapping can assign project roles inside each space assignment. Sync permissions on each login re-evaluates those bindings at every login.

Use the REST API

POST /v2/resource-restrictions restricts a project or dashboard from its resource_id alone and DELETE /v2/resource-restrictions/{resource_id} removes the restriction. Both require space admin or the equivalent permissions, and restricting a resource that is already restricted has no effect. POST /v2/role-bindings grants a project role on a restricted project. All endpoints are listed in the RBAC REST API.