Applies to:
- Plan -
- Deployment -
Summary
Issue: Creating a custom trace view fails or is blocked unless the user has thecreate prompt permission on the project.
Cause: Custom views are not a separate object type. They are stored as prompt/function rows with function_type = 'custom_view', alongside other project prompts.
Resolution: Grant the user the create prompt permission on the project.
Resolution steps
If a user cannot create a custom trace view
Step 1: Check the user’s project permissions
In Settings > Access control, verify the user has thePrompt: Create permission for the project.
Step 2: Grant the required permission
Assign a role that includesPrompt: Create, or add the permission to a custom role for that project.
Background
Custom views use the same storage layer as prompts. When you create a custom trace view, Braintrust stores the view configuration and generated code as a prompt/function row withfunction_type = 'custom_view'. Because of this, the permission check at creation time is identical to creating a prompt.
| Action | Permission required |
|---|---|
| View a custom trace view | Prompt: Read |
| Create a custom trace view | Prompt: Create |