Each managed client receives a separate assigned connection. The tools and credentials prepared for one organisation must not be reused for another.
Account boundaries#
During onboarding, verify the exact service account, workspace and brand. The same service can contain multiple businesses or workspaces. A successful login or a matching display name alone may not establish that the correct one was selected.
Your connection should expose the agreed tools. If you see another organisation's data or unexpected administration tools, stop using the connection and report the mismatch through your onboarding contact. Share only the minimum evidence needed to identify the problem.
Permission layers#
The MCP connection controls access to the configured operations. The upstream service applies its own permissions, account entitlement and rate limits. Both layers must allow the request.
A read-only workflow should have the narrow tools and service authorisation needed for reads. Do not rely on a tool name or an AI instruction as the only protection against an unwanted change.
Asking for more access#
Describe the new business task, the target account and which actions are needed. DigLab can check the supported API route, service permissions and test requirements. The change should be verified before it becomes part of your regular workflow.
Shared credentials#
Do not share an individual connection credential with unauthorised teammates. Ask DigLab which access arrangement is appropriate for your team and whether a separate credential or connection is needed. Do not put keys in shared prompts, chat histories or public repositories.
See credential safety for secure handling and rotation and offboarding when a person or device stops needing access.