Skip to main content
Version: 0.4

Roles and Permissions

Roles and Permissions​

Konstruct uses role-based access control (RBAC) to manage what users can do across the platform. Roles are assigned to users through their team memberships and SSO group mappings.

Predefined Roles​

Konstruct provides three predefined roles:

RoleDescription
Platform AdminFull access to all resources. Can manage infrastructure, cloud accounts, SSO, and organization-wide settings.
Team AdminCan manage team resources, catalog applications, and deployments. Limited access to clusters (read-only).
DeveloperCan read catalog applications, deploy catalog items, and manage applications. Limited access to clusters (read-only).

Permissions Matrix​

Each role grants a specific set of actions on each resource. The three actions are:

  • Read (R) — View the resource
  • Write (W) — Create or update the resource
  • Delete (D) — Remove the resource
ResourcePlatform AdminTeam AdminDeveloper
applicationR, W, DR, WR, W
app-repositoryR, W, D——
catalog-applicationR, W, DR, W, DR
catalog-deploymentR, W, DR, WR, W
cloud-accountR, W, D——
clusterR, W, DRR
cluster-templateR, W, D——
environmentR, W, D——
git-accountR, W, D——
organizationR, W, D——
pipeline-templatesR, W, D——
ssoR, W, D——
teamR, W, D——

Legend: R = Read, W = Write, D = Delete, — = No access

tip

Platform Admin has full access to every resource. If a resource shows "—" for Team Admin and Developer, only Platform Admins can manage it.

How Roles Are Assigned​

Roles are assigned through team membership and SSO group mappings:

  1. A user authenticates via SSO (e.g., Microsoft Entra).
  2. The user's SSO groups are matched against team role mappings.
  3. If a team maps the user's SSO group to a predefined role, the user receives that role.
  4. A user can hold multiple roles across different teams — the most permissive role applies for each resource.

Role Details​

Platform Admin​

The Platform Admin role is intended for infrastructure engineers and platform operators. It provides unrestricted access to all resources, including:

  • Managing cloud accounts and git accounts
  • Configuring SSO providers
  • Creating and managing cluster templates and pipeline templates
  • Creating organizations and teams
  • Deploying and managing applications and environments
  • Registering app repositories
  • Managing license keys (self-hosted)

Team Admin​

The Team Admin role is intended for team leads who manage their team's resources. Key capabilities:

  • Full management of catalog applications (create, update, delete)
  • Read and write access to catalog deployments
  • Read and write access to applications
  • Read-only access to clusters
  • Create and manage organizations (team management)
  • View SSO groups

Developer​

The Developer role is intended for application developers. Key capabilities:

  • Read-only access to catalog applications
  • Read and write access to catalog deployments
  • Read and write access to applications
  • Read-only access to clusters