Skip to main content

Org scope

The Console has two distinct scopes: project scope and org scope. Every mode page in this section — Admin, Forge, Studio, Workspace — is project scope. When you're in a project, you're working on the things that belong to that project: its members, its data, its functions, its authored views. Org scope is a layer above that. It's where you manage the things that span all your projects: who's in the organisation, which projects exist, how billing rolls up, and what the default email delivery looks like across every project you run.

You reach org scope from the same browser — the URL changes from <orgSlug>.console.k9o.io/@<projectSlug>/… to <orgSlug>.console.k9o.io/org/…. The sidebar changes completely when you cross that boundary.

What's in org scope​

Org scope opens on Projects — a flat list of every project in the org, where you create a project, archive one, or jump into a project's Console. Everything else clusters into four areas of work: managing who's in the org, watching what's happening across it, governing all your projects at once, and configuring org-wide settings.

A note on access first: most of org scope is admin-only. If you're an ORG_MEMBER, you see the projects you've been assigned to and your own profile — the management bands below require an org-admin role.

Managing who's in your org​

Operators lists everyone in the organisation. Invite people here; they join the org with the ORG_MEMBER role automatically, and you assign them to specific projects from here — they don't appear in a project's roster until you do.

Groups are org-wide collections you can use as the unit of assignment when provisioning access across multiple projects, rather than wiring each person project-by-project.

Permissions is the org-level role reference — the read-only matrix of what each org role can do.

Identity Providers is your org's workforce single sign-on. Connect Okta, Microsoft Entra ID, or Google Workspace once and your whole team signs in with corporate credentials — see Enterprise SSO for the per-provider setup guides.

Access Requests is the queue of people asking to join projects in your org — approve or deny, and the grant flows through to the project's roster.

Extensions manages the extensions installed across the org and which projects they're available to.

Watching what's happening​

Audit Log is the org-wide event browser — every consequential action across all your projects, filterable by actor, action, resource, and time.

Rejection Log surfaces injection attempts the platform blocked, aggregated across the org.

SIEM is the org-level forwarding configuration — ship org-scoped audit events to Splunk, Datadog, or an HTTPS endpoint, mirroring the project-level SIEM surface but for org-scoped events. (Org Monitor doesn't carry Attributes — that's a project-plane concern.)

Governing across projects​

This is the cluster that makes org scope worth visiting regularly if you're a compliance-minded admin: it rolls every project's governance up into one place.

Policies is the cross-project aggregate view of every project's policy bundles — spot drift, compare postures, and see at a glance which projects are governed how. It's read-only here; mutation happens in the project (a drill-in link takes you there).

Maker-Checker sets org-wide approval tightening for gated actions, cascading onto every project (projects may tighten further, never loosen).

Gate Approvals is the cross-project aggregate of in-flight irreversible-action gates — every project's pending attestations in one queue.

Session Policy sets the org's session ceiling — see The session-policy ceiling below.

Configuring org-wide settings​

General carries display name and org metadata. Notifications is the org's email delivery configuration (see The email delivery cascade). Billing is invoices, payment methods, and usage across projects. Storage is org-level bring-your-own-storage configuration. Custom Domain wires your own domain to the org's surfaces.

The session-policy ceiling​

Session policy cascades through three tiers: platform invariants → org ceiling → project policy. The platform sets hard invariants no one can loosen; you set an org ceiling at org → Govern → Session Policy; and each project sets its own policy within that ceiling.

The rule is one-directional: a project can always tighten past the org ceiling (shorter sessions, fresher MFA, fewer concurrent sessions), but it can never relax beyond it. If a project admin tries to set a session value looser than your org ceiling, the save is refused — the project's Session Policy surface shows an inline error on the offending field plus a banner explaining the ceiling. To give projects more headroom, you raise the org ceiling first.

If you haven't set an org ceiling, projects are unbounded (subject only to the platform invariants) — so setting a ceiling is the lever for org-wide session-security floors, useful for SOC 2 / FedRAMP / HIPAA postures where you need every project to honour a minimum.

Roles at the org level​

Org roles and project roles are orthogonal — someone can hold an org role and a different set of project roles simultaneously. The platform doesn't derive one from the other.

Org roleWhat it allows
ORG_OWNERFull org administration: all org settings, member management, project provisioning, billing, and the ability to assign any other role
ORG_ADMINSame as owner except cannot remove the owner or transfer org ownership
ORG_BILLING_ADMINBilling access only — invoices, payment methods, plan changes — independent of any other org admin status
ORG_MEMBERAuto-assigned on org invite; grants visibility to the projects list and access to your own /me/* surfaces. No project access until explicitly assigned to a project

Project roles (PROJECT_ADMIN, PROJECT_AUTHOR, PROJECT_EDITOR, PROJECT_MEMBER, PROJECT_VIEWER, PROJECT_ANALYST, PROJECT_AUDITOR) are assigned per project and are independent of org role. PROJECT_MEMBER grants standard read/write access to a project's data surfaces. PROJECT_ANALYST (displayed as Scout in the Console) is a read-only analytical role with access to aggregate views but no mutation capability. A common pattern: an operator holds ORG_MEMBER across the whole org, PROJECT_ADMIN in the production project they own, and PROJECT_VIEWER in two other projects they need read access to.

The email delivery cascade​

Email delivery — invitations, MFA codes, Gate-hosted auth notifications, form submission receipts — follows a three-tier cascade. The platform picks the lowest tier with an explicit configuration:

  1. Project SMTP — if the project has its own SMTP configured (under Admin → Settings → Notifications), the platform uses it for all email originating from that project.
  2. Org SMTP — if no project-level SMTP is set, the platform falls back to the org's SMTP configuration (under org Settings → Email). This affects all projects in the org that haven't set their own.
  3. Platform default — if neither is set, the platform delivers email from its own managed sending infrastructure.

To configure org-level SMTP, go to org Settings → Email. There's a "Send test email" action so you can verify the integration before it affects live traffic. Projects that want to override it set their own SMTP in Admin → Settings → Notifications; projects that don't configure anything automatically inherit the org setting.

Your operator profile — the /me/* surfaces​

The avatar dropdown in the top-right of every Console page opens your operator-self surfaces. These sit at /me/… and are universal — they're the same regardless of which org or project you're looking at, and changes you make here apply everywhere.

SurfaceWhat it covers
ProfileDisplay name and avatar
Account settingsPassword and MFA configuration
SessionsAll active sessions across every org you're a member of
API tokensPersonal access tokens for programmatic platform access (CLI, CI, scripts). Each token is bound to a single (org, project) pair at create time — operating across N projects means N tokens. See Personal access tokens.
NotificationsYour personal notification preferences
Audit logYour own activity — every action you've taken, across all orgs
Data exportRequest a GDPR export of your personal data

These surfaces are accessible no matter which project or org you're currently viewing. If you need to revoke a session or rotate a personal API token, you don't have to navigate to a specific project to do it.

See also​

  • Orientation — the five project-scope modes at a glance.
  • Admin mode — project-level governance (manage, monitor, govern, settings).
  • Vault mode — encryption custody operations on the project.
  • API → Auth — the identity substrate behind org members and providers.