Skip to main content
Applies to:
  • Plan -
  • Deployment -
Summary Goal: Understand which project actions require the update permission in Braintrust. Features: Project-level access control (ACL), permission management, retention policies.

​
What Update Permission Allows

​
Project-Level Resources

  • Project: Edit name and description
  • Project scores: Create, update, delete human review scores (not automated evaluation scores) Separately from the update permission, individual human review scores support an optional visibility setting that restricts which reviewers see a score (by member or permission group) in the review modal. This is distinct from project access permissions and is not a hard access boundary: reviewers with hidden scores can reveal them with the Show all scores toggle. See Restrict score visibility.
  • Project tags: Create, update, delete
  • Span iframes: Create, update, delete
  • MCP servers: Create, update, delete
  • Project automations: Create, update, delete retention policies and other automations

​
Project Resources

  • Experiments: Modify metadata and experiment data
  • Datasets: Modify dataset metadata and rows
  • Logs: Modify logs in the project

​
What Update Permission Does Not Include

  • Delete: Deleting projects or resources requires separate Delete permission
  • Manage access: Changing access permissions requires separate Manage access permission
  • Create: Creating new experiments, datasets, or logs requires separate Create permission