Roles Across Cakewalk

Human Access and Agent Access each define their own roles. This page maps the two sets and points to the full definitions.

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.

---

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

The same person can hold a role in each module.

---

📚 Related

• Platform Overview
• How They Connect