Sources for a client organization
A source feeds one organization. When you add a source for a client organization, its facts, findings and staff belong to that client organization and to nobody else. This page says what changes for a…
Written By Christopher Scaminaci
Last updated 13 days ago
A source feeds one organization. When you add a source for a client organization, its facts, findings and staff belong to that client organization and to nobody else. This page says what changes for a client, vendor by vendor.
At a glance
- What it does: adds a source for one client organization.
- Plan: Pro and above.
- Who: an Administrator.
- Where: choose the client in the AI Governance menu, then Connected accounts → All sources.
The rules for every source
- Only an administrator of your whole account adds a source. A client's own administrator cannot (see Client administrators and auditors).
- Choose the client organization first. As the administrator of your whole account, pick it in the organization picker at the top of AI Governance, then open All sources. The source you add belongs to the organization you picked.
- A new source needs the same things as a new client organization: client organizations switched on for your account, the Pro plan or higher, and a client organization that is Active. If a rule refuses, the page says which one. See Client organizations.
- A source that already runs keeps running if one of those rules changes later. Only closing the client organization stops its sources.
- Closing a client organization switches off its sources. It does not remove the connections you made for it on the Connectors page.
Microsoft 365: the client's own administrator must sign in
Each client organization has its own Microsoft 365 connection, made on AI Governance → Connected accounts → Microsoft 365 with the client organization picked. It is the connection that reads the client's Copilot use and, in the same way, the client's staff list.
Who must sign in. The connection has two steps, and the client's own Global Administrator or Privileged Role Administrator completes both, signing in with an account of the client's directory. An account from your own directory is not enough, even if you have delegated (GDAP) access to the client. The Microsoft sign-in page asks for the account, so arrange for the client's administrator to sign in at that point.
Why. StackJack checks that the account that signs in belongs to the directory being connected. Microsoft's documentation for partners says a partner can consent in a client's directory only with a role the client's own directory grants it. It does not say that a partner's delegated sign-in carries the client's directory identifier, which the check needs. This is not confirmed against a live client directory. If a delegated sign-in does carry it, this rule can be relaxed. Until then, ask the client's administrator.
The directory trap. One Microsoft 365 directory can be connected to one organization in a region. If you try to connect a directory that is already connected, the page says: "That Microsoft 365 directory is already connected to another StackJack organization. Contact support if you believe that is wrong." So:
- Do not connect the same client's directory to two client organizations.
- Do not connect a client's directory to a client organization if the same directory is already connected to your own organization (for example, a client that shares your tenant).
- If an organization is connected to one directory and you need another, Disconnect first. The page says: "This organization is already connected to a different Microsoft 365 directory. Disconnect it first, then connect the other one."
Disconnect switches off only the Microsoft 365 sources of that client organization. It does not touch any other organization.
The staff of a client organization
A client organization's people come from its own Microsoft 365 directory, not from your team and not from your directory sync. If you try to turn those on for a client organization, the page says: "A client organization's people come from its own Microsoft 365 directory. It cannot import your own members or your directory sync."
- The import reads the client's users through the read basic profiles permission (
User.ReadBasic.All). Microsoft's description of that permission does not include whether an account is enabled. So StackJack imports every user it is shown, disabled accounts included. A person who is removed from the directory is marked as removed on the next pass. - With no connected directory, nothing is imported and the client organization's staff list stays as it was.
- A client organization whose place is the European Union or the United Kingdom imports nothing until its staff notice is published, the same rule as for your own organization.
- One pass adds at most 200 new people. A larger directory is added over several passes.
Anthropic, OpenAI, GitHub and Google Workspace: one named connection per client
These sources read through a connection on the Connectors page. Your default connection reads your own account. For a client:
- On the Connectors page, add a named connection for the connector, made with the key or sign-in of the client's own account with that vendor.
- When you add the source for the client organization, choose that connection in the Connection list.
The source reads that connection and no other, never your default one. Use one connection for each client.
The Gemini, Vertex AI and AWS Bedrock sources work the same way for a client. Create them with the client organization picked, and use the client's own Google Workspace connection, Google Cloud project or AWS account. See Gemini activity and conversations, Vertex AI request-response logs and AWS Bedrock invocation logs.
OTLP sources and settings for the client's computers
- A client organization has its own OTLP ingest address and token. Send a client's AI tool telemetry to that client organization's own source only.
- A client organization has its own delivery targets: how its settings reach its computers through your RMM. The settings file and installer for a client organization name that client's token and targets only.
- These files carry the account's token, so only an administrator of your whole account can download them. A client's own administrator cannot.
DefensX: one customer per client
A DefensX source for a client organization reads one DefensX customer: the client's, and never your own. When you add the source for a client organization, you must type the DefensX customer id. The dialog says: "The client's customer id in your DefensX partner portal. This source reads that customer's web activity and never your own." Without it, the page says: "Enter the client's DefensX customer id."
- If DefensX does not find that customer, the source shows the state defensx-customer-not-found and reads nothing. Check the customer id, and check that your partner key still reaches the customer.
- Today, one DefensX connection can feed one client customer only. Store your DefensX partner key once for each client, each under a connection name of its own.
Island: one connection per client
Island does not document a read across several client tenants under one partner key, so StackJack does not offer one. One Island key belongs to one Island tenant. To govern a client's Island browsers, make a named Island connection with a key from that client's own Island tenant, and add the source for the client organization on that connection. This is not confirmed as a limit of Island's product. It is what Island's published documentation allows today.
Cloudflare AI Gateway: one connection per client
Cloudflare reads AI gateway logs per account. For a client, make a named Cloudflare connection that names the client's Cloudflare account id, with a token that has AI Gateway Read on that account. Add the source for the client organization on that connection.
- Use one connection for each client. If one token can list several client accounts, the source would put all of their gateway logs into one client organization.
- StackJack did not find a way to list a partner's client accounts through one Cloudflare token. This is not confirmed against a live partner setup.
Was this helpful?
More in For MSPs
All clientsClient organizationsAI exposure scanProspectsStill need help? Ask the team