Skip to main content
For MSPs

Client administrators and auditors

You can invite a person from a client, or an adviser that works for the client, to one client organization only. That person signs in to AI Governance and sees that client organization and nothing…

Written By Christopher Scaminaci

Last updated 13 days ago

You can invite a person from a client, or an adviser that works for the client, to one client organization only. That person signs in to AI Governance and sees that client organization and nothing else of your account. This page says how to invite them, what they can do, and what stays with you.

At a glance

  • What it does: lets a client's own people see their client organization and nothing else of your account.
  • Plan: Pro and above.
  • Who: an Administrator of the MSP account invites. The client administrator sees one client.
  • Where: AI Governance → Organizations → Client organizations, then the client's page.

Roles

A person can hold one or more of these four roles. The roles are the same as in your own organization.

RoleWhat it allows
AdministratorChanges settings, rules and roles of the client organization.
ReviewerReads activity and findings, and can ask to see a person's name.
Reveal approverApproves requests to see a person's name (never their own).
AuditorReads records and the audit trail. Changes nothing.

Invite a person to one client organization

  1. Open AI Governance → Organizations → Client organizations, and open the client organization.
  2. Under Roles, select Grant roles or invite someone. The Roles page opens for that client organization.
  3. Under Invite someone outside your organization, type the email address, the first name and the last name, and tick the roles.
  4. Send the invitation.

The invitation email is the same one described in Get started with AI Governance. The link works only for the address it was sent to. If the email or the sign-in could not be created, the page says so, and Resend tries again.

A person who is already a member of your own organization is given roles from the same Roles page, scoped to the client organization.

When you cannot invite. The same rules as for adding a client organization apply. You cannot invite or grant while client organizations are switched off for your account, while your plan is below Pro, or while the client organization is Closing or Closed. A role that already exists keeps working while it is Active or Closing, and the roles of a Closed client organization are revoked.

One kind of role per person

A person holds either roles for your whole account or roles for single client organizations. Never both. If you try to give a person a second kind, the page says: "This person already holds roles of the other kind: either for the whole account or for single client organizations, never both. Revoke those roles first."

To give one person access to two clients, invite them to each client organization. Each invitation names one client organization.

Sign-in

Every role needs a sign-in through your organization's single sign-on, or a sign-in that used a second factor. This is the same rule as for your own roles. See Get started with AI Governance.

What a client administrator can do

An Administrator of a client organization can change these things inside that client organization:

  • The staff notice and the name policy.
  • The data-loss rules and the client names dictionary.
  • The TypeSafe AI opt-in, and the other judgment settings.
  • The AI tools mode.
  • Requests to see a person's name, findings, and the staff and identity lists.
  • Data subject requests and erasure.
  • Policies, training, incidents, evidence packs, the inventory decisions and tool requests.
  • The roles of that client organization (grant, change, revoke, invite).

What stays with you

These stay with an administrator of your whole account, because each one stores a credential, sends data out of StackJack or costs money:

  • Billing and the plan.
  • Sources, ingest tokens and content exclusions.
  • Connector connections and the Microsoft 365 connection.
  • Delivery targets and endpoint settings.
  • Vendor keys, personal keys and budgets.
  • The MCP proxy, hook endpoints, the AI gateway and its lanes, and the bypass.
  • Archive and main store targets, alert channels and the Teams bot.
  • Changes in your AI vendor accounts.
  • Legal holds and the keep times.
  • The place of a client organization, and adding, closing or reopening a client organization.

A client administrator does not see the pages for these. The person sees only the client organizations they hold a role in (an organization picker appears when there is more than one), and the pages for billing, sources, the Microsoft connection, endpoint settings, hooks, the AI gateway, the MCP proxy, archive targets, vendor changes, setup, the browser extension, Cloud AI and the list of client organizations are not offered. A client administrator who needs one of these asks you.

Files that carry your account's ingest token, such as the endpoint settings files and installers, are not available to a client administrator. The download answers "not found".

Remove a person's access

Open the Roles page of the client organization and revoke the roles. When a client organization is closed, its roles are revoked. The record of who held roles is kept.