Learn about capability-based access control for SaaS deployments
In Splunk Agent Observability, capability-based access tokens and collaborator roles determine the actions that a user can perform on a resource.For an action to be allowed, both of these conditions must be met:
The access token contains the matching capability.
The user has the required collaborator role for the resource.
This page describes capability-based access control and the available capability keys.
Collaborator roles don’t apply to global evaluators or groups. Group access is based on group membership or visibility.
When a resource is shared with a user in the UI, the user is granted a collaborator role that sets a resource-level ceiling on the actions they can perform. The user’s access token must still contain the required capability for them to perform a given action.The following table describes resource access by collaborator role:
Resource
Owner
Editor
Annotator
Viewer
Projects
Manage the project, including sharing.
Work with runs, data, annotations, Agent Streams, evaluator settings, and controls.
View the project and record human feedback.
View the project.
Datasets
Manage, share, and delete the dataset.
Update, rename, and export the dataset.
Not offered.
View the dataset.
Prompts
Manage, share, and delete the prompt.
Update the prompt.
Not offered.
View the prompt.
Annotation queues
Manage, share, and annotate the queue.
Not offered.
View the queue and record annotations.
Not offered.
LLM integrations
Creator only: Manage the integration and view its credentials.
SHARED actions apply to a shared resource. For example, a project used by multiple people. SHARED isn’t a blanket permission. It doesn’t add you as a collaborator or elevate your role.
ALL actions apply across the organization.
GLOBAL actions only apply to evaluators, which don’t use collaborator roles.