> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/human-access-and-agent-access/how-human-access-and-agent-access-connect.md). # How They Connect 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](https://www.cakewalk.security/docs/human-access/how-to-guides/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. :bulb: *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](/docs/connections-and-integrations/hris-and-idp.md). *** ### 🔑 How Someone Gets Agent Access 1. An Admin grants Agent Access to whole groups so new members hold it automatically, or the person [requests it](https://www.cakewalk.security/docs/human-access/how-to-guides/requests) like any other App. 2. The request runs your company's approval workflow. 3. Once granted, the person opens Agent Access from the profile menu and connects their first Agent. See [Switching Modules](/docs/human-access-and-agent-access/switching-between-human-access-and-agent-access.md). *** ### 👁 What Each Module Shows * **In Human Access**: who holds Agent Access, alongside every other App. Agents and Connections discovered at the [MCP Gateway](https://www.cakewalk.security/docs/ai-agent-access/concepts/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](https://www.cakewalk.security/docs/ai-agent-access/concepts/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](/docs/human-access-and-agent-access/user-lifecycle.md). *** ### 📚 Related * [User Lifecycle](/docs/human-access-and-agent-access/user-lifecycle.md) * [Switching Modules](/docs/human-access-and-agent-access/switching-between-human-access-and-agent-access.md) * [HRIS and IdP](/docs/connections-and-integrations/hris-and-idp.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.cakewalk.security/docs/human-access-and-agent-access/how-human-access-and-agent-access-connect.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.