Organizations and roles
An organization owns your clusters, projects and integrations; roles decide what each member can see and change.
An organization is the top-level account in Kapten. It owns your clusters, projects and integrations such as GitHub, and it is the unit you are billed for. You can belong to several organizations and switch between them.
Members
People sign in to Kapten with their email address: Kapten sends them a one-time sign-in link, there is no password. A user is a member of an organization while they hold at least one of its roles.
Roles
A role is a named set of permissions. Every organization starts with three built-in roles, which cannot be changed:
| Role | Can do |
|---|---|
owner |
Everything, including deleting the organization. |
admin |
Everything except deleting the organization. |
member |
Belong to the organization and see its access control. Nothing else until given more. |
Custom roles
To give someone access to only part of the organization, create a custom role. A role is a list of grants: a permission, such as environment:create or project:delete, applied to a scope:
- the whole organization,
- all resources of a type, such as every project,
- or selected instances, such as one project or one environment.
Roles only add permissions: a member holding several roles can do everything any of them allows. A grant on a project includes read access to everything inside it, including environments created later. A grant on an environment lets the member read its project, but not the project’s other environments.
Deleting resources
Kapten only deletes a resource once it is empty: you cannot delete a project that still has environments, or an environment that still has pipelines. Delete what it contains first.
Activity
Every change made in an organization is recorded with who made it and when. Members allowed to read it find it in the organization’s activity log.