Central RBAC
Manage accounts, groups, and product permissions with central RBAC in Loopback. Learn how sign-in, API tokens, and technical service credentials work together.
Manage accounts, groups, and product permissions with central RBAC in Loopback. Learn how sign-in, API tokens, and technical service credentials work together.
Who may manage a cluster, create a bucket, or push an image to the Registry? Each additional service increases the number of access paths your team needs to organize.
Loopback manages these permissions through central, platform-wide Role-Based Access Control, or RBAC. Accounts, organizations, and groups provide the shared framework. Within it, you define who may use which products and functions.
An application often uses several services. It runs on Kubernetes, stores files in Object Storage, and retrieves its images from a Registry. Bundles control its deployment.
Different people and processes work with these services. Developers need access to their applications' resources. The platform team maintains the infrastructure. Automated workflows publish artifacts or make API calls.
Access management needs to reflect these tasks. This means concrete actions: viewing resources, changing configurations, running deployments, or publishing images.
A central permissions model lets you consider these decisions together. You manage access to individual products within the same organization.
In Loopback, each person has an individual account. Membership associates that account with the company's organization.
This separation makes the access structure clear: the account represents a person, while the organization provides the shared framework for teams, resources, and permissions.
| Component | Purpose |
|---|---|
| Account | A person's identity |
| Organization | The company's shared framework |
| Membership | Associates an account with the organization |
| Group | Brings together members and assigned permissions |
| Product permission | Controls access to a product's functions |
Further permission assignments build on this structure. Group membership and assigned permissions can reflect the tasks a person performs.
When several people perform the same tasks, groups provide a way to assign shared permissions.
In Loopback, you can create groups with their own fine-grained permissions. Each group receives the permissions its members need for their area of work.
Start your planning with the actual tasks:
This might lead to groups for platform administration, application development, and release management. These names are possible team conventions. What matters is the tasks and permissions you associate with them.
A clear structure also makes later changes easier. When responsibilities shift, you can review the relevant groups and permissions deliberately.
Shared RBAC means permissions are managed centrally. At the same time, each product has its own functions and corresponding permissions.
Kubernetes, Object Storage, Registry, and Bundles are therefore considered individually within the same model.
| Product | Examples of access tasks to clarify |
|---|---|
| Kubernetes | View and manage clusters |
| Object Storage | Manage buckets and associated access credentials |
| Registry | Manage repositories and publish or retrieve artifacts |
| Bundles | Manage applications and deployment workflows |
The table shows tasks for permission planning. You determine the specific permissions each group receives based on the product functions it needs.
A team can use several services while receiving suitable permissions for each. Management remains central, while permissions reflect the respective tasks.
Access management involves two related questions: who is signing in, and what may that person do afterward?
Sign-in establishes identity. Permissions determine which functions are available to that identity within the organization.
Loopback supports SSO and connections to external identity providers. People can also add OTP and passkeys to their accounts.
These sign-in methods complement the permissions model. Successful sign-in gives access to the account. Rights within the organization continue to follow the permissions assigned there.
Plan these aspects together when introducing the platform: how should people sign in, how will they become organization members, and which groups match their tasks?
Alongside the interface, API calls can access platform functions. Loopback supports API tokens per user account for this purpose.
Calls made with a token run with the permissions of its associated account. This relationship matters for planning: the account's permissions also determine what the API calls can do.
Before setting up an automated workflow, define which actions it should perform and which account permissions it needs.
The Registry additionally provides robot accounts and credentials for automated push and pull access. This offers a separate mechanism for accessing images and Helm charts.
API tokens and Registry credentials therefore belong in the same automated access plan, while serving different purposes.
Even with central management, it helps to examine the different access layers precisely.
For example, a person may have permission to manage Object Storage in Loopback. An application accesses stored objects through the access keys intended for that purpose.
The Registry follows a similar distinction: managing the product and accessing artifacts automatically each have their own requirements.
| Access type | Purpose |
|---|---|
| Platform permission | Use a product's functions in Loopback |
| API token | Make API calls with a user account's permissions |
| Object Storage access key | Enable technical access to the S3 service |
| Registry credentials | Enable automated access to images and charts |
Consider these layers together for a complete access structure. This keeps it clear which people manage resources and which technical credentials applications or workflows use.
A permissions structure needs to evolve with your team. New people join, tasks change, and projects finish.
Groups provide a clear starting point. When a person takes on a new task, you can check their membership against the existing structure. When a task ends, you can review the permissions associated with it.
The same applies to technical credentials. When your team or a workflow changes, review which API tokens, access keys, and Registry credentials are still needed.
A useful approach connects permissions with clear responsibility: each group has an understandable purpose, and each technical credential belongs to a known task.
With central RBAC, you manage access to your stack within one organization. Accounts represent people, groups bring shared tasks together, and product-specific permissions control access to the respective functions.
SSO, OTP, and passkeys complement sign-in. API tokens and product service credentials enable automated workflows.
You can organize your team's access structure in one place and align it with the different tasks across the platform.
Start with managed Kubernetes, object storage, registry, or Bundles. One account, one permission model.