Overview
Every member of a Taskade workspace holds one role. The role decides what the person can do: edit projects, run agents, invite teammates, or manage billing. Pick the lightest role that lets the person do their job. That choice keeps your workspace secure and your seat count predictable.
TL;DR: Taskade grants access by role, from Owner down to Viewer. Owner and Maintainer control billing, membership, and roles. Editor covers most teammates who build. Checker and Viewer fit reviewers and read-only stakeholders. Per-project sharing adds one-off guests. Pair roles with SAML single sign-on, available from the Business plan up.
Compare the workspace roles
Read the ladder from the top down. A higher role can do everything the roles below it can do. For the cascade across workspace, folder, and project, see User Roles & Permissions.
| Role | What they can do | Typical use |
|---|---|---|
| Owner | Everything below, plus delete the workspace and hand it to someone else | Workspace founder, account holder |
| Maintainer | Invite or remove members, change roles, manage billing, full editing access | Day-to-day workspace lead |
| Editor | Create and edit projects, run agents and automations, invite members | Most teammates who build daily |
| Checker | Complete assigned tasks, tick checklists, comment | Voters, light contributors, task owners |
| Viewer | Read projects and leave comments | Observers, review-only stakeholders |
Marketing copy describes this ladder as role-based access from Owner to Viewer. The in-app member list can show a shorter label for a role. The permissions stay the same.
People outside your workspace hold no workspace role. Reach them through per-project sharing instead. See Share a Project.
Check what every role can do
Find the action you care about, then read across to see which roles allow it.
| Action | Owner | Maintainer | Editor | Checker | Viewer |
|---|---|---|---|---|---|
| View a project | Yes | Yes | Yes | Yes | Yes |
| Comment on a task | Yes | Yes | Yes | Yes | Yes |
| Complete an assigned task | Yes | Yes | Yes | Yes | No |
| Edit any task | Yes | Yes | Yes | No | No |
| Create a project | Yes | Yes | Yes | No | No |
| Create an agent | Yes | Yes | Yes | No | No |
| Add an automation | Yes | Yes | Yes | No | No |
| Invite a member | Yes | Yes | Yes | No | No |
| Change someone's role | Yes | Yes | No | No | No |
| Delete a project | Yes | Yes | No | No | No |
| Manage billing | Yes | Yes | No | No | No |
| Delete the workspace | Yes | No | No | No | No |
| Leave the workspace | No | Yes | Yes | Yes | Yes |
Two rows surprise people. A Viewer can still comment, so a read-only stakeholder can give feedback without an upgrade. An Owner cannot leave a workspace, so hand the workspace over first. See Transfer Ownership.
Change someone's role
Open the Members panel and switch a role in a few clicks.
- Click the dropdown arrow next to your workspace name.
- Pick Members.
- Find the person you want to change.
- Click their current role.
- Pick a new role, then confirm.
The change applies at once. The member sees the new permissions on their next page load.
Set a different role on one project
When the workspace role is too tight or too loose, set a project role. The workspace role is the baseline. The project role is an override that applies inside that project only.
- Promote a workspace Viewer to Editor on the one project they help build.
- Lock a workspace Editor down to read-only on a sensitive project.
- Invite a guest with no workspace seat to a single project as a comment-only collaborator.
See Share a Project for the per-project share dialog and the guest options.
Manage access to a Taskade Genesis app
Publish a Taskade Genesis app and you gain a second audience: the people outside your workspace who use the app. Manage those people through App Users, not through workspace roles. App Users sign in to the published app. They never see your billing, your members, or your other projects.
Use workspace roles for the teammates who build the app. Use App Users for the public who run it.
Clear up common confusion
- A workspace can have more than one Owner. Adding a second Owner does not remove the first. This helps co-founders.
- An Owner cannot leave a workspace. Transfer ownership first, then leave. See Transfer Ownership.
- Roles are workspace-scoped, not account-scoped. A teammate can be Owner of one workspace and Viewer of another.
- A lower role applies at once. A demoted Editor loses edit rights on their next page load.
- Billing is not Owner-only. A Maintainer can also manage billing, so name that role with care.
Related guides
- Transfer Ownership. Hand off the Owner seat without losing the workspace
- Invite Members. Add teammates and assign a starting role
- Workspace Privacy. Control who sees what across folders and projects
- Share a Project. Per-project overrides and guest sharing
- SAML SSO with Google. Centralized sign-in, available from the Business plan up