Guides
How to do each task in GovernanceOS, step by step, with a link to the screen where it happens.
Getting started
What GovernanceOS keeps, and the first step for a practitioner and for an institution.
What GovernanceOS records, and what a gate is
The record of each AI decision: five gates, one named approver at each, and evidence hashed as the gate passes.
Sign up with your work email, request your access code, and start the 7-day trial when you enter the access code.
Claim your institution’s tenant
An administrator signs in with the institution’s identity provider, names the register owner and claims the tenant.
Practitioners
Running governance work for clients, from a new workspace to the handover.
Create one workspace per client, or one for your own institution, with its regime profile and a reason.
Import a register from a spreadsheet
Upload a CSV or XLSX register, map its columns, and import every row as a typed value.
Read the import receipt and the findings
See what an import wrote, then read the findings: typed versus produced, point in time, and re-assertion lapses.
Write a finding that cites records, says what they show and who decides, then share it with the client.
Record the client’s authorization, then upload documents or connect a GitHub repository, read-only.
Hand a workspace to the client
Send the claim to the client’s administrator. After the claim, you keep a read-only copy.
Apply to be listed in the directory
Consultants apply at the last step of sign-up, or later from Account. A Directory editor approves each listing by hand.
Institutions
Setting up the tenant, signing gates, keeping evidence current and answering an examiner.
Say where you are supervised, what you are and what you answer to, and sign each change with a reason.
Invite members and give gate authority
The CISO invites people at the institution’s domain and gives each a role, with the gate authority it carries.
Read the gate record and its evidence, then sign, return or reject it with a reason, as the named approver.
Attach the report, record the findings, what was not examined and any dissent, then sign G2.
Re-assert evidence before it lapses
As the model owner, confirm an entry is still true, say what that rests on, and sign before the interval runs out.
Build and share an evidence pack
Choose the systems and dates, sign the pack with a cover note, and share it with an examiner key.
Give an examiner read-only, time-boxed access, with every read logged, and revoke it at any time.
Examiners and audit
Reading an institution's records under a key, and checking a pack yourself.
Open the records an institution shared with you, with a one-time code. No sign-up and no password.
Ask in plain words, check how the question was read, and keep a permalink to the answer.
Download the verifier and the pack, check their SHA-256, run it with --key and the pack key hash you were sent, and read the result.
Account and support
Signing in, checking our emails, and reaching us.
Sign in with codes or an authenticator
Sign in with a code from your email, or turn on an authenticator app and keep your recovery codes.
Check that an email came from us
Every email from GovernanceOS carries a check code. Look it up yourself before you trust the email.
Get support or report a barrier
Use the support form on Help. Any address works for a barrier report, with no plan and no account.
No guide matches. Contact support, and a person replies by email.
Need a person? Help and support.