Why does my agent have its own login instead of using mine?

This is one of the most important differences between a Workforce agent and most other AI tools, and it's a deliberate design choice, not a limitation.

Many AI copilots work by borrowing your session — your OAuth tokens, your connected accounts, your local files — to act "on your behalf." That's convenient, but it means the agent's access is exactly as broad as yours, every action is commingled with your own activity, and revoking it means touching your own account.

A Workforce agent instead gets its own accounts, provisioned like a new hire's: its own email address, its own login to your CRM, its own Slack identity, its own credentials vault. That gets you:

• Least-privilege access — your agent only has the access it actually needs for its work, not blanket access to everything you personally can touch.

• A clean audit trail — every action the agent takes is attributed to its own identity, not blended into a human teammate's activity log.

• No delegation risk to your own accounts — nothing about your agent's access depends on sharing your password, session, or personal OAuth grant with it.

• Independent, instant revocation — if you ever need to shut off an agent's access, you disable its account, full stop. No need to rotate your own credentials or worry about what else was tied to that session.