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

# Permission group not working: Project-level scorer access

export const plans_0 = "Any"

export const deployments_0 = "Any"

export const data_plane_version_0 = undefined

export const use_case_0 = undefined

<Note>
  **Applies to:**

  * Plan - {plans_0}
  * Deployment - {deployments_0}
  * {data_plane_version_0}
  * {use_case_0}
</Note>

# Project-level permission groups do not grant cross-project scorer access

## Summary

Project-level permission groups let users work within a specific project and its child objects. They do not let users browse scorers that live in other projects. To view scorers across projects in the UI, the user also needs an organization-level permission group with **Projects > Read** enabled.

If you need narrower access, use the API to grant organization-level project `Read` restricted to `prompt`, which is where scorers reside. The standard permissions UI does not expose that prompt-only restriction.

## Why this happens

* Project-level permissions only apply to the project where they are granted.
* Shared scorers are stored as prompts, and cross-project scorer discovery is checked through organization-level project read access.
* Users can belong to multiple permission groups. Their effective permissions are the union of all grants.

## Recommended fix in the UI

Create a separate organization-level permission group for shared scorer visibility, then add the user to both groups:

1. Go to **Settings** > **Organization** > **Permission groups**.
2. Create a new permission group, or edit an existing organization-level group used for shared scorer access.
3. Open **Permissions** for that group.
4. Under **Projects**, enable **Read**.
5. Save the group.
6. Add the affected user to:
   * their project-scoped permission group
   * the organization-level scorer-visibility group
7. Refresh the playground or automation rules editor and verify the scorer list appears.

This keeps the user's project-specific permissions separate from the broader scorer-discovery permission.

## API-only least-privilege option

If organization-wide **Projects > Read** is too broad, create the scorer-visibility grant through the API instead of the UI:

* `object_type = org_project`
* `permission = read`
* `restrict_object_type = prompt`

This grants cross-project scorer visibility without broad project read. Use this path when you want access limited to prompts and scorers rather than all project resources.

## Notes

* If the user still cannot see scorers, verify that the scorer exists in another project and that the user still has the required project-level access for the project where they are working.

## References

* [Access control](/admin/access-control)
* [Administration overview](/admin)
* [ACLs API](/api-reference/acls/list-acls)
* [Groups API](/api-reference/groups/list-groups)