> For the complete documentation index, see [llms.txt](https://alludium.gitbook.io/alludium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alludium.gitbook.io/alludium-docs/12.-workspace-overview/12.3-roles-and-permissions.md). # Roles and Permissions Workspace roles define what actions people can take within a workspace. Roles are assigned when inviting members and can be modified by users with the required administrative access. The People page exposes three workspace roles: Owner, Admin, and Member. Enterprise configuration, feature flags, and workspace-specific settings can affect the exact actions available to each role, so use this page as product guidance rather than a complete permission matrix. ## Owner Owners have the broadest workspace responsibility. Owners typically manage: * Workspace settings and governance * People, roles, and ownership continuity * Billing, plans, and usage controls * SSO and authentication settings where available * Admin configuration surfaces such as agents, integrations, automations, project setups, and task types Every workspace must have at least one Owner. If you are the only Owner, the system should prevent you from leaving or removing yourself until another Owner exists. ## Admin Admins manage much of the operational setup for a workspace. Admins may manage: * People and non-owner memberships * Workspace configuration * Agents, templates, and skills * Integrations, connections, and tools * Automations and execution logs * Project setups and task types where enabled Ownership-level actions remain restricted to Owners. ## Member Members are the default day-to-day users of a workspace. Members typically use: * Inbox and tasks * Projects and project-specific workflows * Files * Personal account settings * Role-appropriate workspace settings views Members usually do not manage workspace-level configuration surfaces such as Agent Builder, Skills, Integrations, Automations, Project Types, Task Types, billing, SSO, or role changes. These surfaces may be hidden from the Member sidebar. Members cannot invite users, change workspace roles, or remove workspace members. ## Changing Member Roles **Location:** Settings -> People Owners can change or remove other members, including Admins and Owners, as long as the workspace keeps at least one Owner. Admins can invite members and manage non-owner members, but they cannot change or remove Owner-level memberships. Members cannot invite users, change roles, or remove workspace members. To modify a member's role when you have access: 1. Navigate to **People**. 2. Find the member in the list. 3. Open the role control next to their name. 4. Select the new role. 5. Confirm the change. Role changes take effect immediately. The member's access and visible navigation update to reflect the new role. ## Role Assignment Best Practices * Assign Owner role only to senior leadership or people responsible for workspace continuity. * Use Admin role for team leads and managers who need operational configuration access. * Assign Member role to practitioners who primarily complete tasks, work in projects, and use files. * Review roles regularly and adjust as responsibilities change. * Maintain at least two Owners to ensure administrative continuity. ## Shared Agent Permissions Shared-agent behavior can vary by agent, connection scope, and workspace configuration. Treat agent building, sharing, and workspace-wide deployment as Administration work unless your workspace has explicitly enabled a broader model. Members may use shared or configured agents through the surfaces made available to them, such as tasks, projects, files, or shared assistants. --- # 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: ``` GET https://alludium.gitbook.io/alludium-docs/12.-workspace-overview/12.3-roles-and-permissions.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.