Roles
Roles for workspaces and orgs and permissions per role
Last updated
Roles for workspaces and orgs and permissions per role
Takeaways
A role controls what a user can do: install, publish, run evals, manage members, or administer a workspace.
Roles are assigned per workspace, so a user can hold different roles in different workspaces.
Separate organization-level roles, member and admin, govern org-wide actions such as creating workspaces.
Roles are assigned per workspace. To learn more about creating a workspace, see Workspace management.
Can view and install private plugins in the workspace
✅
✅
✅
✅
✅
Can see other users in the workspace and their permissions
✅
✅
✅
✅
Generate workspace scoped API keys
✅
✅
✅
✅
Review, security-scan, and fix agent skills from the CLI (tessl review run, tessl review run security, tessl review fix)
✅
✅
✅
✅
Generate eval scenarios
✅
✅
✅
Run evals
✅
✅
✅
Manage eval visibility
✅
✅
✅
Create and publish plugins
✅
✅
✅
Unpublish plugin (within 2 days of publishing)
✅
✅
✅
Rolling out plugins (to repositories)
✅
✅
✅
Setup and manage integrations
✅
✅
Invite users and change user permissions
✅
✅
Can remove other managers
✅
✅
Archive plugins
✅
✅
Edit / delete workspace scoped API keys
✅
✅
Add/remove other owners from workspaces
✅
Delete the workspace
✅
View skill inventory, scans, findings, committers, and breakdowns
✅
✅
✅
✅
✅
Run a skill inventory import or trigger a rescan
✅
✅
✅
Ignore or unignore repositories
✅
✅
Create or delete a skill inventory, enable automatic scanning, and manage private indexing
✅
✅
View org
✅
✅
Manage org scoped API keys
✅
Create workspaces
✅
Inherit owner on every workspace in the org
✅
Last updated