Skip to main content
Start

Roles and who can do what

AI Governance has four roles of its own. They are separate from team roles in StackJack. A person can hold one role or several. The role decides which pages the person sees and what they can change.

Written By Christopher Scaminaci

Last updated 13 days ago

AI Governance has four roles of its own. They are separate from team roles in StackJack. A person can hold one role or several. The role decides which pages the person sees and what they can change.

At a glance

  • Plan: every plan.
  • Who: a governance administrator gives and removes roles.
  • Where: AI Governance → People → Roles.

The four roles

RoleWhat it allows
AdministratorChanges settings, sources, rules and roles. Decides tool requests.
ReviewerReads activity and findings. Can ask to see a person's name. Triages findings and alerts.
Reveal approverApproves requests to see a person's name. Never approves their own.
AuditorReads records and the audit trail. Changes nothing.

The account owner of your StackJack account holds every role automatically. The Roles page lists the owner as "Held automatically".

A person who holds no governance role is staff. Staff see My AI activity only. See What staff can see about themselves.

Sign-in rules

Every role needs a sign-in through your organization's single sign-on, or a sign-in that used a second factor. Staff do not need one. If a person signs in with a password, they add an authenticator app or a passkey first, and then select Sign in again.

Who sees which page

A page that your role does not allow is not in your menu. This table shows the pages by role. "Any role" means Administrator, Reviewer, Reveal approver or Auditor.

Area and pageWho sees it
OverviewAny role
Overview → All clientsAdministrators who can see every organization of the account (not a person limited to one client)
Get startedAdministrator
Activity → Activity explorerReviewer, Administrator
Activity → FindingsReviewer, Administrator
Activity → SpendAny role
Alerts → InboxAdministrator, Reviewer. A Reveal approver sees only the alerts about name requests.
Alerts → IncidentsAny role
Alerts → Alert settingsAdministrator, Reviewer, Auditor. Only an Administrator can change anything. The others read.
AI inventory → InventoryAny role
AI inventory → Tool requestsAny role
AI inventory → Vendor changesAdministrator
Compliance → Readiness, AI use policy, AI training, Report packsAny role
Compliance → Audit trailAdministrator, Auditor
People → StaffAdministrator, Reviewer, Reveal approver
People → Staff sign-insAdministrator, Reviewer, Reveal approver
People → RolesAdministrator
People → Data requestsAdministrator
Data sources → StatusAdministrator, Auditor
Connected accounts → All sourcesAdministrator, Auditor
Connected accounts → Microsoft 365, Cloud AIAdministrator
Staff computers → Coverage, Endpoint agent, Coding tools, Claude hooksAdministrator, Auditor
Staff computers → DeployAdministrator
Staff computers → Browser extensionReviewer, Administrator. Only an Administrator can change it.
AI traffic → AI gateway, MCP proxyAdministrator
Rules → Rule packsAny role
Rules → AI judgmentsAdministrator, Reviewer, Auditor
Rules → Client namesAdministrator
Organizations → My organization, Client organizations, Prospects, Report brandingAdministrator of your whole account
Privacy and data → Privacy and notices, Retention and holds, Security scanningAdministrator, Auditor
Privacy and data → Storage archiveAdministrator
Settings → AI assistant, Close AI GovernanceAdministrator, Auditor
Settings → BillingAny role. Only the account owner buys or changes a plan.
My AI activityStaff

A person who works for a client organization sees only that client's pages. Settings that belong to the whole account, such as Billing, Sources, the gateway and the archive, are not offered to them. See Client administrators and auditors.

Names

The role has a Sees names setting. Under the pseudonymous name policy, nobody sees a staff name without an approved reveal. A reviewer asks to see a name. A reveal approver decides, and it is recorded. See Staff and sign-in matching.

Give a role to a team member

  1. Open AI Governance → People → Roles.
  2. Under Give a team member a role, choose the team member.
  3. Tick every role they should hold. Choosing someone who already holds a role replaces their roles with the ones you tick.
  4. Choose whether the person Sees names, and select Save roles.

Revoking a role takes effect at once. Select Revoke on the person's row.

Invite an auditor or adviser from outside your organization

Someone who is not a member of your organization is invited by email. The invitation works only for the address it was sent to. They get an email, sign in with a second factor, and see only what their roles allow.

  1. On the Roles page, find the panel Invite someone outside your organization.
  2. Enter the email address and the first and last name.
  3. Tick the roles they should hold, and select Send invitation.

The invitation email.

Subject: You have been invited to AI Governance at

invited you to review its AI Governance records, with a role it chose for you.

Select the button to sign in and accept. Use the email address this message was sent to; the link works only for that address.

The link works until UTC. After that, ask to send a new invitation.

If you were not expecting this, ignore this email. Nothing changes until someone signs in with this link.

What the join page says.

  • When it works: You now have access to AI Governance for .
  • A link that does not work: This invitation link is not valid or has expired. Ask the person who invited you for a new one.
  • A different account: This invitation is for a different email address. Sign out and sign in with the invited address.
  • A person whose access was removed: Your access to this organization was removed. Ask its administrator.
  • An invitation that was used already: This invitation was already used.
  • A fault: We could not accept the invitation just now. Nothing was changed. Try again in a moment.

What the administrator sees on the Roles page.

  • Inviting people from outside your organization is not set up for your region yet.
  • The invitation was saved, but a sign-in could not be created for that address just now. Select Resend to try again.
  • The invitation was saved, but its email could not be sent. Select Resend to try again.

Roles in your AI tool

The same roles decide what a person can ask for or do from an AI tool such as Claude or Copilot. See Use AI Governance from your AI.

Next