Skip to main content
Version: 0.5

Konstruct 0.5.1

Released: May 2026

Highlights​

  • Per-organization permissions — your role is evaluated against the organization you're acting on, not your highest role anywhere
  • Global API keys — generate one key that works across every organization you belong to
  • All your keys, in one view — find single-org and global keys together without switching organizations

Per-organization Permissions​

Earlier 0.5.x releases evaluated permissions globally — if you were Platform Admin in any organization you belonged to, you got Platform-Admin authority everywhere. 0.5.1 evaluates your role per organization instead. The org you have selected in the Viewing as switcher decides which role applies.

A user mapped to Platform Admin in one organization and Developer in another now has Platform-Admin authority only in the first one. Admin-tier actions in the second show as unavailable; read-only actions still work.

Within a single organization, if you belong to multiple teams that map you to different roles, the highest of those roles applies — same as before.

See Roles and Permissions → Roles Are Scoped to Organizations for a worked example.

Global API Keys​

When you generate an API key, you can now choose between two scopes:

ScopeWhen to use it
One organizationScripts, CI jobs, or MCP clients that only ever touch that org.
All your organizationsCross-org automation, personal CI tokens, or AI assistants that need to act across the organizations you belong to.

A global key inherits whatever role you have in each org at issue time. There's no role picker — Konstruct snapshots your current memberships. If you join a new org or your role changes after the key is generated, revoke and re-issue.

See API keys → Choose a Scope for the create flow.

All Your Keys, in One View​

The API keys page filtered by the org selected in Viewing as, which made global keys hard to find. 0.5.1 adds an All your keys view that surfaces every key you own — single-org and global keys together — so you don't have to remember which org a key was issued under. View activity and Delete work the same way from the unified list.

Upgrade​

Update targetRevision to 0.5.1 in your Konstruct Argo CD Application manifest, keeping the required global values from 0.5.0:

spec:
  source:
    chart: konstruct
    repoURL: oci://europe-west2-docker.pkg.dev/civo-com/charts
    targetRevision: 0.5.1
    helm:
      values: |
        global:
          selfHosted: "true"
          bootstrap: "false"

Commit and push — Argo CD syncs the new version automatically.

API keys created on 0.5.0 and earlier remain valid and keep their original scope.