Getting started

Claim your institution’s tenant

An administrator signs in with the institution’s identity provider, names the register owner and claims the tenant.

How-to video coming soon

For: Institution administrators
You need: Administrator rights in your institution’s Microsoft Entra, Google Workspace or Okta.
Result: The tenant, with its first facts written as version 1.

Steps

On Sign in with your institution, choose Microsoft, Google or Okta. Nobody at an institution has a GovernanceOS password.
On Claim your institution’s tenant, check the organization your identity provider verified, then choose the register owner and the accountable executive. Inviting people now is optional.
Still on Claim your institution’s tenant, confirm you may act for the institution, accept the Register tier terms, and choose Claim the tenant. Nothing is created until you claim.
On Set up the tenant, write the regime profile with a reason, set the re-assertion interval in days, and review where the register is stored.
If a practitioner handed a workspace to you, accept or decline it on A workspace handed over to you.
Continue on Set up, the first screen in the tenant: members, settings and assistants, keys, the inventory and the boundary, in any order.

The tenant is tied to the directory identifier your identity provider verifies, not to the domain name.
Not an administrator? The sign-in screen gives you a ready message, with the link, to send to your IT administrator.
Your organization’s consent settings may ask an administrator to approve GovernanceOS first. Okta needs GovernanceOS added as an application before anyone signs in.
A tenant is claimed once, by its institution’s administrator. If yours is already claimed, ask to be invited.
Each fact written at setup can be changed later, with a reason.

These open the prototype, on fictional institutions. People are shown as roles.