Overview
Every member of a Taskade workspace has one of seven roles. Each role unlocks specific actions: edit projects, run agents, publish a Taskade Genesis app, manage billing, invite teammates. Pick the lightest role that lets the person do their job. That keeps your workspace secure and your billing predictable.
TL;DR: Taskade uses a 7-tier permission model: Owner, Maintainer, Editor, Commenter, Collaborator, Participant, Viewer — never "Admin". Owner and Maintainer control billing, security, and roles. Editor and Commenter cover most teammates. The lower three (Collaborator, Participant, Viewer) fit guests, voters, and read-only stakeholders. Per-project sharing extends the picture for one-off external collaborators. Pair with SAML SSO on Business and above for centralized sign-in.
The 7 workspace roles
Read the table top to bottom. Higher roles inherit everything below them. For the cascade across workspace → folder → project, see User Roles & Permissions.
| Role | What they can do | Typical use |
|---|---|---|
| Owner | Manage billing, transfer ownership, delete the workspace, full editing access | Workspace founder, account holder |
| Maintainer | Invite or remove members, manage roles below them, full editing access | Day-to-day workspace lead |
| Editor | Create, edit, and delete any project; run agents and automations; publish a Taskade Genesis app | Most teammates contributing daily |
| Commenter | Read everything, leave comments and suggestions, no direct edits | Reviewers, stakeholders giving feedback |
| Collaborator | Run agents and automations on shared projects, complete tasks, comment | Contractors and partners with scoped access |
| Participant | Interact with checklists, complete assigned tasks, comment | Voters, audience members, light contributors |
| Viewer | Read-only access | Observers, audit-only stakeholders |
People outside your workspace are not assigned a workspace role. They are reached through per-project sharing instead. See Share a Project.
What every role can do
Find the action you care about, then read across to see the lowest role that allows it.
| Action | Owner | Maintainer | Editor | Commenter | Collaborator | Participant | Viewer |
|---|---|---|---|---|---|---|---|
| View a project | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Comment | Yes | Yes | Yes | Yes | Yes | Yes | No |
| Complete an assigned task | Yes | Yes | Yes | No | Yes | Yes | No |
| Edit any task | Yes | Yes | Yes | No | No | No | No |
| Create a project | Yes | Yes | Yes | No | No | No | No |
| Add an automation | Yes | Yes | Yes | No | Yes | No | No |
| Publish a Taskade Genesis app | Yes | Yes | Yes | No | No | No | No |
| Invite a member | Yes | Yes | No | No | No | No | No |
| Manage billing | Yes | No | No | No | No | No | No |
| Delete the workspace | Yes | No | No | No | No | No | No |
Change someone's role
Open the Members panel and switch a role in two clicks.
- Click the ˅ arrow next to your workspace name and pick Members.
- Find the person you want to change.
- Click their current role.
- Pick a new role from the dropdown.
- Confirm.
The change takes effect immediately. The member sees the new permissions on their next page load.
Project-level overrides
Set a different role on a single project when the workspace role is too tight or too loose. The workspace role is the floor. The project role is an override that applies only inside that project.
Common patterns:
- A Viewer in the workspace can be promoted to Collaborator on a single project they help with.
- A Collaborator in the workspace can be locked down to read-only on a sensitive project.
- A guest with no workspace seat can still be invited to a single project as a comment-only or view-only collaborator.
See Share a Project for the per-project share dialog and external guest options.
Roles for Taskade Genesis apps
Publish a Taskade Genesis app and you have a second audience to think about: the people outside your workspace who use the app. Those people are managed through App Users, not through workspace roles. App Users sign in to the published app, not to your workspace, and they never see your billing, members, or other projects.
Use workspace roles for teammates who build the app. Use App Users for the public who consume it.
Common confusion points
- There is no "Admin" role. Maintainer is the closest equivalent. If a teammate asks for "admin access", give them Maintainer.
- A workspace can have more than one Owner. Adding a second Owner does not remove the first. Useful for co-founders.
- You cannot remove yourself if you are the only Owner. Promote someone else to Owner first. See Transfer Ownership.
- Roles are workspace-scoped, not account-scoped. A teammate can be Owner of one workspace and Viewer of another.
- Lowering a role is instant. A demoted Collaborator loses edit rights on their next page load.
Related guides
- Transfer Ownership — Hand off the Owner seat without losing the workspace
- Invite Members — Add teammates and assign their starting role
- Workspace Privacy — Control who sees what across folders and projects
- Share a Project — Per-project overrides and external guest sharing
- SAML SSO with Google — Centralized sign-in on Business and above