Set the regime profile

Steps

1. Open Regime profile. It shows the jurisdiction, the sector, the regimes, and the version with its reason.

2. Choose Change the profile, with a reason. On Change the profile, pick where you are supervised, what you are, and the regimes you answer to.

3. Give the date it takes effect, as YYYY-MM-DD, and a reason. Then choose Review the rows this arms on Change the profile: which rows are kept, which load, and which are written as not yet covered, requested.

4. Sign with your identity provider. The profile is saved as a new version, and the Regulatory change triggers re-arm.

5. Check the Tier profile: the records each gate requires, by tier.

Good to know

• The CISO or the Compliance lead changes the profile, and each change is a versioned record.
• Setup wrote the first version when the tenant was claimed.
• Crosswalks to the EU AI Act, the NIST AI RMF and ISO/IEC 42001 are informative only, never a compliance claim.
• A regime the corpus does not hold yet is written as “not yet covered, requested”, with the date.
• The tier profile is the institution’s own. GovernanceOS enforces it and never sets a tier.

Where in the product

• Regime profile
• Set up the tenant

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

Related guides

• Claim your institution’s tenant

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

• 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.

• 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.