> 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/concepts/roles-across-cakewalk.md).

# Roles Across Cakewalk

Each module of Cakewalk has its own role model, sized to what it governs. This page is the map; the full definitions live in each module's own docs.

### 👥 Human Access Roles

Human Access governs the access lifecycle, so its model distinguishes designated roles from inherited ones:

* **User**: requests access, views own permissions, completes assigned reviews.
* **Admin**: full platform access, covering apps, users, policies, integrations and settings.
* **General Manager**: senior leadership; access requests auto-approve past the manager step.
* **Manager** (inherited): anyone with direct reports; approves their reports' requests.
* **App Owner** (inherited): assigned per App; approves requests and handles reviews for that App.

Full definitions: [Human Access Roles & Permissions](https://www.cakewalk.security/docs/human-access/concepts/cakewalk-roles-and-permissions).

***

### 🤖 Agent Access Roles

Agent Access governs runtime activity, so its model is flat:

* **Admin**: manages Connections and Policies, with org-wide visibility into every Agent and every action.
* **Member**: connects to apps, sets up Agents and responds to approval prompts; sees only their own Connections, Agents and sessions.

Full definitions: [Agent Access Roles and Permissions](https://www.cakewalk.security/docs/ai-agent-access/concepts/roles-and-permissions).

{% hint style="info" %}
The same person can hold a role in each module.
{% endhint %}

***

### 📚 Related

* [Platform Overview](/docs/introduction/platform-overview.md)
* [How They Connect](/docs/human-access-and-agent-access/how-human-access-and-agent-access-connect.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/concepts/roles-across-cakewalk.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.