> 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/platform-overview/human-access-and-agent-access.md).

# Human Access & Agent Access

- [How They Connect](https://www.cakewalk.security/docs/platform-overview/human-access-and-agent-access/how-human-access-and-agent-access-connect.md): How the two modules of Cakewalk work together: one User directory, access owned by Human Access and agent activity visible in both modules.
- [Switching Modules](https://www.cakewalk.security/docs/platform-overview/human-access-and-agent-access/switching-between-human-access-and-agent-access.md): Move between Human Access and Agent Access from your profile menu, and what a grayed out entry means for you or your company.
- [User Lifecycle](https://www.cakewalk.security/docs/platform-overview/human-access-and-agent-access/user-lifecycle.md): What joining, changing roles and leaving mean across Human Access and Agent Access, from the first onboarding task to the last agent session.


---

# 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/platform-overview/human-access-and-agent-access.md?ask=<question>&goal=<endgoal>
```

`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.