> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Resource Restrictions

> Restrict a project, dashboard, or prompt so that only the people you add can access it.

Resource restrictions limit a project, dashboard, or prompt to the people you choose. Normally these resources inherit access from their space, which means everyone in the space can open them. Restricting a resource removes that inherited access, so only the people you add and space admins can open it. This lets you keep sensitive data in a shared space without giving the whole space access to it.

## 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](https://storage.googleapis.com/arize-assets/doc-images/project-config-resource-restriction.webp)

Add each person who needs access and give them a project role. Setting the project back to **Unrestricted** restores space-level access.

## 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](https://storage.googleapis.com/arize-assets/doc-images/dashboard-manage-access.webp)

## 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](https://storage.googleapis.com/arize-assets/doc-images/prompt-manage-access.webp)

## 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.

## Use the REST API

`POST /v2/resource-restrictions` restricts a resource 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. Dashboards can be restricted through the API as well.

All endpoints are listed in the [RBAC REST API](/docs/ax/security-and-settings/sso-and-rbac/rbac-rest-api.md).