How They Connect
How the two modules of Cakewalk work together: one User directory, access owned by Human Access and agent activity visible in both modules.
When your company runs both modules of Cakewalk, they behave as one platform. This page explains what is shared, where access is granted and what you see in each module.
📖 Key Concepts
Human Access decides who holds access. Granting and removing it, including access to Agent Access itself, happens there.
Agent Access is governed like any other App. It can be granted to whole groups automatically, requested by an individual and checked in access reviews.
Activity flows back. The Agents employees run, and their Connections (the apps those Agents connect to), appear in Human Access, so the directory stays complete.
💡 Why this matters: One module is the system of record for who holds access. The other is the system of record for what Agents do with it. Neither duplicates the other's job.
🗂 One User Directory
Your company's HRIS or IdP syncs into Human Access, and Agent Access works from the same set of Users and their attributes. You do not connect your HRIS twice, and the department, title, team and location that Agent Policies evaluate come from the same source as everything else. See HRIS and IdP.
🔑 How Someone Gets Agent Access
An Admin grants Agent Access to whole groups so new members hold it automatically, or the person requests it like any other App.
The request runs your company's approval workflow.
Once granted, the person opens Agent Access from the profile menu and connects their first Agent. See Switching Modules.
👁 What Each Module Shows
In Human Access: who holds Agent Access, alongside every other App. Agents and Connections discovered at the MCP Gateway (the checkpoint every agent action passes through) appear as part of the directory.
In Agent Access: the Agents, their Connections and their activity, plus the Policies (the rules that decide each agent action) that govern them.
Managing who holds access stays in Human Access: adding or removing people happens there, and Agent Access links you across when a task belongs in the other module.
🔒 Removing Access
Removing someone's Agent Access, whether by request, review outcome or offboarding, removes their access and revokes the Connections they hold. For the full picture across joining, moving and leaving, see User Lifecycle.
📚 Related
Last updated
Was this helpful?