Run Commands

Authorization (RBAC)

Learn how to set up and manage Role-Based Access Control (RBAC).

You can use Pachyderm’s Role-Based Access Control (RBAC) model to configure authorization for your users. Users can be assigned roles that grant certain permissions for interacting with Pachyderm’s resources.

Authorization Model #

Users Types #

User TypePrefixDescription
IdP UseruserAny user or group of users authenticated by your Identity Provider to access Pachyderm.
Robot UserrobotA Service account used for third party applications/systems integrating with Pachyderm APIs/Clients.
Pipeline UserpipelineAn internal Service Account used for Pipelines when interacting with Pachyderm resources.
All Cluster UsersA general subject that represents everyone who has logged in to a cluster.

Resource Types #

Resource TypeDescription
ClusterA set of nodes for running containerized applications. Containers allow users to run repeatable and standardized code.
ProjectA project is a container of 1 or more DAGs that allows for users to organize their repos. Projects allow multiple teams to work in a cluster.
RepoA repository is where data is stored and contains both files and folders. Repos tracks all changes to the data and creates a history of data changes.

Role Types #

Role TypeDescription
Cluster RolesGranted at the cluster level.
Project RolesGranted at the project level.
Repo RolesGranted at the repo level or at the cluster level.

License Expiration #

When an Enterprise License expires, a Pachyderm cluster with enabled User Access Management goes into an admin-only state. In this state, only ClusterAdmins have access to the data stored in Pachyderm. This safety measure keeps sensitive data protected, even when an enterprise subscription becomes stale. To return the cluster to its previous state, run pachctl license activate and submit your new code.