Skip to content

Organizations ​

Organizations keep tenants apart: every org-scoped resource - flows, runs, devices, sites, secrets, variables, repositories, schedules - lives in exactly one organization, and what you see everywhere in the app is the active organization's data. Installed plugins and user accounts are platform-level and shared.

Switching organizations ​

The organization switcher sits in the sidebar. Your active organization determines every list and every action, and references across organizations are rejected by design. The one deliberate exception is the designated shared organization: while it is active, its resources are readable - read-only - from every other organization.

If you switch while you have one item open - a flow, a run, an edit form - you land on that item's list in the new organization, because the item itself stays in the organization you left.

Rows that came from the shared organization carry a Shared badge in every list. If you are a member of that organization, the badge is clickable and switches you into it - the shortest path from "I can see this but not change it" to the place where you can. Non-members see the badge as a plain label.

A shared item is read-only outside its organization wherever it appears: its list row and its own page offer no Edit, Delete or other change (no Test or Sync either, for those that have them), only Duplicate where the item has it, which makes an editable copy of your own.

A shared flow can be run from your organization: Run, on its card or on its page, starts a run that belongs to your organization. It targets your devices and uses your variables, with the shared organization's filling in the names yours do not set. To change the flow itself, Duplicate it (in the card's menu or on its page) into an editable copy of your own.

Linking into an organization ​

Your active organization is remembered per browser, so a link to one organization's run or flow, opened by someone whose browser last used another, would find nothing. A link can name its organization by adding ?org= with the organization's slug or id to any page's address:

text
https://hegemony.example.com/runs/<run id>?org=clm
https://hegemony.example.com/flows?org=6f1c2d3e-…

When the page opens, Hegemony switches to that organization first - the way the switcher does, so it stays your active organization afterwards - and then takes org out of the address. If you are not a member of it (platform admins may open any organization), a notice above the page says so and the page shows your own active organization instead; the notice does not say whether such an organization exists. If you are a member but the organization fails to load, the notice says it could not be opened just now; open the link again to retry. Other parameters, such as the run list's filters, are kept.

Tools that link into Hegemony - the certificate lifecycle pack's NetBox links, a chat notification, a ticket - should add ?org=<slug> to every link they build. A link opened in a new tab or window that has to sign in first still lands on the page it names, ?org= included.

Roles are per organization ​

Your role - and therefore what you can do - is granted per organization: you can be an admin in one organization and a viewer in another. The permissions reference lists what each role allows.

The app shows the actions your role in the active organization allows: a list leaves out the row actions you may not use, and a page shows its buttons disabled, with the reason when you point at one. A form you may not use, opened by its address, says so instead of failing when you save.

Managing organizations ​

Under Settings → Organizations, platform admins can:

  1. Create an organization with a name and slug.
  2. Open an organization's detail to edit it.
  3. Manage members: add users and assign their role in that organization.

Creating, editing, and deleting organizations is reserved for platform admins. An organization's own admins manage that organization's members and IdP mappings, but cannot create or edit organizations themselves.

Deployments that sign users in through an identity provider can map IdP groups to organizations and roles automatically - see IdP organization mapping.

History card ​

The detail page carries a History card listing the most recent audit log entries about this object: how long ago, what the action was, which fields changed, who did it, and a non-success outcome where there was one. A row opens the same entry dialog the audit log uses, and the card links into the log filtered to this object. It appears only for callers who may read the audit log, so a viewer or approver sees the page without it.

Access review ​

For a periodic review of who can do what, a platform admin can download one list of every user, the organizations and roles they hold, and the API tokens issued to them:

bash
curl -H "Authorization: Bearer hgm_pat_xxxx…" \
     -o access-review.csv \
     "https://hegemony.example.com/api/platform/access-review?format=csv"

Use a token created by a platform admin for Platform (all organizations) with the admin scope. An organization admin cannot download the list, because it spans every organization.

  • Formats: format=json (the default) nests roles and tokens under each user; format=csv has one row per organization role or token, and one row with access none for a user who has neither. A cell that a spreadsheet would run as a formula is written as text.
  • Revoked tokens are left out unless you add include_revoked=true. Active and expired tokens are always listed, with their status.
  • Last login is the last time the user used the app after signing in, to within a minute. Using an API token does not change it; the token's own last use is in its row.
  • Tokens without a user: a token belongs to a username. A token whose username has no user record (for example, one that has never signed in) is listed under tokens_without_user in JSON, and as a row with an empty sub in CSV.
  • Not included: platform roles such as admin. They are granted in Keycloak (or the identity provider behind it), so review them there: in the Keycloak admin console, Realm roles → admin → Users in role. That tab shows only users given the role directly, so also check the groups that grant it.

Every download is recorded in the audit log as entity.exported, with the format and the number of users and tokens.

Released as open source under the AGPL-3.0-or-later license. Development is sponsored by Rexonix s.r.o. Contact — [email protected].