Platform Overview
What Human Access and Agent Access each govern, where the line between them falls and what to expect when your company runs one or both.
Cakewalk is one platform with two modules. Human Access governs the access your people hold. Agent Access governs what AI agents do with that access at runtime.
📖 The Map
Governs
Who holds access to which apps, at which permission level
What an Agent may do, evaluated per action
Unit of decision
Access: requested, approved, provisioned, reviewed, removed
An agent action: Auto-approve, Require approval or Deny
Built on
Your company's HRIS or IdP as the source of truth for people
The MCP Gateway, Cakewalk's checkpoint between Agents and their apps
Question it answers
"Who has access to what, and is it still right?"
"What are our Agents doing, and was each action allowed?"
💡 Why this matters: The two modules answer different questions about the same people. Knowing which one you are in tells you where a task lives.
🧭 Where the Line Falls
Human Access decides who holds access. Agent Access decides what happens inside a delegated session. Agents do not get identities of their own: an Agent acts on behalf of the person who delegated the task and never gets more access than that person holds.
An example: a developer gets GitHub through Human Access, granted with their team's defaults or through an approved request. When their coding Agent writes to GitHub, each action passes the MCP Gateway and is evaluated against Policies that know the developer's department, title, team and location.
🏝 Running One
Each module works on its own. A company can run Human Access without Agent Access, or the other way around. Your profile menu shows both modules; a module your company does not have appears grayed out. See Switching Modules.
🤝 Running Both
With both modules live, they share one foundation:
One HRIS or IdP connection feeds one User directory. See HRIS and IdP.
Agent Access is granted and governed from Human Access, like any other App.
Offboarding covers app seats, Agents and Connections in one flow. See User Lifecycle.
For the mechanics, see How They Connect.
📚 Related
Last updated
Was this helpful?