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

# Restrict user access to specific projects only

> [!NOTE]
>
> **Applies to:**
>
> * Plan - Enterprise
> * Deployment - Self-hosted
> *
> *

Summary

Configure project-level access restrictions by removing default read permissions at the organization level and manually granting read access on specific projects. For infrastructure isolation with separate AWS accounts, use separate organizations as each requires its own data plane, though both can share the same license contract.

## Configuration Steps

### Step 1: Find your organization name

Log in to Braintrust, click your organization name in the upper-left corner, hover over the current organization, and select **Copy organization name** to copy the exact name (including any whitespace). See [Find your organization ID](https://docs.braintrust.dev/admin/organizations.md#find-your-organization-id).

### Step 2: Configure base organization permissions

Navigate to your organization settings and set the default permissions to only allow create, update, and manage access. Remove read access from the base permission level to prevent users from seeing all projects.

### Step 3: Grant project-specific read access

Go to each individual project's settings and manually add read access for specific users. This ensures users can only see the projects they've been explicitly granted access to.

### Step 4: Create separate organizations for infrastructure isolation (if needed)

If you need separate AWS accounts and data planes (e.g., for testing infrastructure upgrades), create separate organizations. Each organization requires its own data plane but can be added to the same license contract.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.