> For the complete documentation index, see [llms.txt](https://notara.gitbook.io/notara-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notara.gitbook.io/notara-docs/team/roles.md). # Roles Notara has four roles, ordered from least to most privileged: `member < editor < admin < owner`. Every role includes all permissions of the roles below it. ## Role Comparison | Permission | Member | Editor | Admin | Owner | | ----------------------------------------- | :----: | :----: | :---: | :---: | | Message the agent in Slack | ✓ | ✓ | ✓ | ✓ | | View dashboard (read-only) | ✓ | ✓ | ✓ | ✓ | | Create and edit skills | | ✓ | ✓ | ✓ | | Fork platform skills | | ✓ | ✓ | ✓ | | Create and manage libraries | | ✓ | ✓ | ✓ | | Upload documents | | ✓ | ✓ | ✓ | | Create automations (scheduled + webhooks) | | ✓ | ✓ | ✓ | | Connect and manage tool connectors | | | ✓ | ✓ | | Manage BYOK API keys | | | ✓ | ✓ | | Invite and remove team members | | | ✓ | ✓ | | Change team member roles | | | ✓ | ✓ | | Configure channel settings | | | ✓ | ✓ | | Manage tool permission overrides | | | ✓ | ✓ | | Approve tool calls (approval flow) | | | ✓ | ✓ | | Manage groups | | | ✓ | ✓ | | Create MCP endpoints | | | ✓ | ✓ | | Manage billing and subscription | | | | ✓ | | Manage workspace settings | | | | ✓ | | Transfer ownership | | | | ✓ | | Delete workspace | | | | ✓ | ## Member The default role for anyone new to the workspace. Members can interact with the Notara agent in Slack — they can send messages, get responses, and use any tools that have `open` permission. They can view the dashboard in read-only mode. **Members cannot:** * Create or modify skills, libraries, or automations * Connect or modify tool connectors * Change any workspace configuration Members are the consumers of the workspace — they benefit from the skills, context, and tools that editors and admins have set up. ## Editor The **empowerment threshold**. An editor can build and maintain the team's skills and context without needing full admin access. This is a deliberately powerful role that doesn't require sharing credentials or billing access. An editor can: * Write and fork skills (custom prompts for the team's workflows) * Build and maintain context libraries (upload documents, configure load policies) * Create scheduled automations and webhooks * Build the knowledge base that makes the agent smarter An editor **cannot**: * Connect or reconfigure external tool integrations (e.g., add a new Stripe key) * Add or remove team members * Approve tool calls in the approval flow * Grant elevated permissions to skills or tools This separation is load-bearing: if editors could grant tool permissions, then a malicious or mistaken skill could escalate tool access without admin awareness. ## Admin Admins manage the operational layer: what tools are connected, who's on the team, how channels are configured, and what tools are approved when they come through the approval flow. An admin is typically the workspace owner's trusted delegate — a technical lead, ops manager, or team lead who manages the setup. **Admin-specific responsibilities:** * **Approval flow**: when a write tool triggers an approval request, it goes to the first available admin's Slack DM. Admins are responsible for reviewing and approving or denying these requests. * **Connector management**: adding, updating, and removing tool connector credentials. * **Permission overrides**: setting tenant-level and channel-level tool permission overrides. * **Team membership**: inviting and removing members, changing roles. ## Owner The owner has full control of the workspace, including billing. Each workspace has exactly one owner. **Owner-specific capabilities:** * Manage the Stripe subscription (upgrade, downgrade, cancel) * View and export billing history * Change workspace-level settings (name, Slack integration, etc.) * Transfer ownership to another admin Ownership is typically the founder or the person who set up the Notara workspace. If the owner leaves the organization, transfer ownership to a remaining admin before deactivating their account. ## Assigning Roles To change a team member's role: 1. Go to **Settings → Team**. 2. Click the member's current role badge. 3. Select the new role from the dropdown. 4. The change takes effect immediately. An admin cannot promote someone to owner (only the owner can transfer ownership). An admin can promote members to editor or other admins. --- # 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://notara.gitbook.io/notara-docs/team/roles.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.