Skip to main content

User Management

Scope uses role-based access control (RBAC) to manage what users can do within the platform. This page covers the available roles, their permissions, and how to manage team access.

Roles

Scope defines three roles with increasing levels of access:

RoleDescription
ViewerRead-only access to prompts, versions, and traces
EditorFull prompt management — create, edit, test, and promote prompts
AdminEverything Editors can do, plus provider/key management and user administration

Permissions Matrix

ActionViewerEditorAdmin
View prompts and versionsYesYesYes
View tracesYesYesYes
View providers (list)YesYesYes
Create promptsYesYes
Edit prompt metadataYesYes
Create/edit versionsYesYes
Test prompts (execute)YesYes
Promote to productionYesYes
Archive/unarchive versionsYesYes
Manage golden setsYesYes
Configure providersYes
Manage API keysYes
Manage users and rolesYes
Delete promptsYes
Delete providersYes

Managing Users

Invite a User

  1. Go to Settings > Users
  2. Click Invite User
  3. Enter the user's email address
  4. Select a role (Viewer, Editor, or Admin)
  5. Send the invitation

The invited user receives an email with instructions to access Scope.

Change a User's Role

  1. Go to Settings > Users
  2. Find the user in the list
  3. Click their current role to open the role selector
  4. Select the new role
  5. Save the change

Role changes take effect immediately.

Remove a User

  1. Go to Settings > Users
  2. Find the user in the list
  3. Click Remove
  4. Confirm the action
warning

Removing a user revokes their access immediately. Resources they created (prompts, versions) are preserved.

Best Practices

  • Principle of least privilege — assign the minimum role needed. Most team members should be Editors; reserve Admin for those who need to manage providers and keys
  • Separate admin accounts — avoid using admin accounts for day-to-day prompt work
  • Regular access reviews — periodically review the user list and remove access for team members who no longer need it
  • Audit trail — promotion history and version metadata track which user performed each action
Was this page helpful?