What the manager can do
The manager receives employee-level administration for that worker, including access outside its ordinary team or role audience. This authority covers the following areas, subject to applicable product restrictions such as release-managed configuration.
Selected editors can receive permission to change particular settings areas. They do not become the accountable manager, and an editor assignment does not by itself grant access to the worker.
See Governance for the access and editing controls, and Approvals for reviewing proposed actions. Manager status does not mean every action automatically pauses for approval: configure the policy deliberately.
Why the manager matters for credentials
When a verified member asks for work interactively, that member supplies the user scope. The manager does not replace that identity merely because the member lacks a connection. For governed background work, the manager supplies the user scope when automation is authorized. Admitted external contacts without a member identity can also use the manager as the accountable credential subject. This has two practical consequences:- User-scoped integrations: The manager needs the appropriate connection and provider permissions for unattended work that uses it.
- Vault API keys: The manager must explicitly share the required keys with the worker. Assigning a manager does not automatically share their Vault.
Selecting the manager’s credential scope is not the same as lending the
manager’s full permissions. Background work needs its own active
authorization, and external work remains limited by its channel admission.
Credentials alone do not authorize unrelated actions.
What manager status does not grant
Managing one AI Employee does not automatically grant:- Organization-wide administration, billing management, or authority over other workers.
- Access to every workflow, document, knowledge source, or connected application.
- The ability to inspect another person’s Vault or retrieve reusable secret values through the protected Vault interface.
- Broader provider permissions than those granted to the connected identity or key.
- Permission to bypass tool restrictions, outbound-recipient rules, or required approvals.
- Unrestricted access to other members’ conversations. Conversation use and visibility follow their own policies.
Change managers safely
Follow Hand over an AI Employee for a worked transfer, connection preparation, access-removal checks, and a handover acceptance checklist. A manager change is a security handover, not just an organizational update. Changing the manager revokes affected employee automation grants; do not assume existing unattended work will continue without review and renewed authorization.1
Review the worker's responsibilities
Inventory scheduled actions, event-based work, connected channels, sensitive
tools, and pending approvals.
2
Prepare the replacement
Confirm the new manager is an active account member. Connect the user-scoped
applications they need and explicitly share any required Vault keys with the
worker.
3
Transfer the assignment
Save the new manager in Governance. Review the worker’s audience, selected
editors, and conversation-sharing choice as part of the handover.
4
Review and reauthorize unattended work
Review affected automations, restore authorization through the supported
controls, and test representative work before relying on it.
5
Remove obsolete access
Remove old Vault grants and unnecessary connections as appropriate. Revoke
provider credentials separately when required by your offboarding process.

