Roles & Permissions
Create roles, choose their module access and permissions, set the default role for new members, assign roles to people, and look up every permission with the Member and Admin defaults.
On this page
A role is a named set of capabilities. Every member holds exactly one, and it decides what they can do across the organization: which modules they see, what they can create, what they can change, and which settings they can reach. Roles are one half of the access model; the other is per-object Sharing & Access. If you are new to the split, read Understanding Permissions first.
The built-in roles#
Every organization starts with three. Admin and Member are ordinary roles you can rename, retune, or delete; Owner is not.
| Role | What it holds | Notes |
|---|---|---|
| Owner | Everything, always | Locked: no rename, edit, or delete. Exactly one per organization, and at least one active member must hold it. Only an Owner can give someone the Owner role. |
| Admin | Every permission in the matrix | Operationally the same as Owner; the difference is that it can't promote anyone to Owner. Every permission added later reaches it when the permission ships. |
| Member | The contributor set: create and manage your own items, workstreams, comments, and time entries; create and manage your own boards, Gantts, automations, saved views, item templates, and API keys; open the Service Desk and send public replies. Module Access to Map, Boards, Gantt, Items, Automations, and Templates, but not Reports or Settings. | The starting point for a new member unless you change the default. |
Defaults describe newly created organizations
These defaults are seeded when an organization is created, and DevStride rarely adds to Member or custom roles afterwards, so an organization created some time ago, or one whose roles have been edited, may differ. Admin roles (any role except Owner that holds Manage Permissions) are the exception: in every organization they hold every permission, and each new one reaches them when it ships. A permission someone had removed from an Admin role on purpose came back once, in November 2026; an Owner can narrow the role again, and nothing grants it back later. Time Entry Access is not affected, because switching it off takes access away: an Admin role with it off stays that way and doesn't gain the three time-entry permissions. The matrix on the Permissions page is always the truth for your organization.
The Permissions page#
Open Configure Settings, then under Admin choose Permissions.
- The Roles rail on the left lists every role. The Owner is pinned at the top with a lock. Each other role has three icons: a pin (filled on the role that is the default for new members; click a hollow one to make that role the default), a pencil to Rename role, and an x to Delete role.
- New Role at the top of the rail creates a role.
- Selecting a role shows its detail on the right: the name and description, a banner reading Editing permissions here affects N members with their avatars (or "No members are currently assigned to this role"), then Module Access, then Permissions.
Toggles save the moment you flip them. There is no Save button and no draft state, so read the affected-members banner before you start.
Create a role#
- Click New Role.
- Enter a Name and, optionally, a Description ("what does this role do?"), then click Create role. The role starts with nothing switched on.
- Switch on the modules the role should see under Module Access.
- Switch on its capabilities under Permissions. Each row shows the permission's name, a one-line description, and, where it applies, a Requires: line naming its prerequisites.
Prerequisites cascade#
Permissions form a ladder: Manage All … requires Manage Own …, which requires Create …; comments and time entries require Create Items And Workstreams; every Settings permission requires the Settings module. Switching a permission on also turns on everything it requires. Switching one off also turns off everything that depends on it. So turning off Create Items And Workstreams silently removes comments, time entries, and both Manage tiers for items; check the matrix afterwards.
Two toggles that work in reverse#
Time Entry Access (under Time Entries) and the per-plugin rows under Module Access are on for every role by default. Switch Time Entry Access off to remove every time-entry surface from the role: the item drawer's Time Tracking tab, the sidebar's Time Spent control, and the time-spent cell in the Items table. The three time-entry permissions beneath it turn off and read "Unavailable while Time Entry Access is off for this role" until you switch it back on.
Module Access#
| Module | What it opens |
|---|---|
| Map | Map Value (the workstream portfolio) |
| Boards | Plan Delivery: boards, folders, and cycles |
| Gantt | Track Progress |
| Reports | Measure Performance (the reports still need the matching Read Report … permissions) |
| Automations | Automate Workflows |
| Items | The Items list |
| Settings | Configure Settings (each section inside also needs its own Manage … permission) |
| Service Desk | The Service Desk module, once the desk is enabled for the organization |
| Templates | The Templates module |
A module switch controls the sidebar entry and the route only. It does not change what the API or MCP tools allow, and a module can be locked on when a permission the role holds needs it ("Required by capability permissions this role holds").
Plugin menus#
Enabled plugins appear in the navigation for every role by default. To take one away from a role, switch off that plugin's row in the role's Module Access ("Turn off to block this plugin's menu item"). This hides the menu entry only; it grants or removes no other permission, and roles you have not touched keep seeing every plugin.
Set the default role for new members#
Click the hollow pin on a role in the Roles rail. New invitations take that role automatically; existing members are unaffected. The default role can't be deleted until you point the default at another role, and the Owner role can't be the default.
Rename or delete a role#
Use the pencil and x icons in the Roles rail. A role with members still assigned can't be deleted; move them to another role first. The Owner role can't be renamed or deleted.
Assign a role to a member#
- Open Configure Settings, then under Organization choose Users. The Access role column shows each member's role.
- Open the member's Edit User dialog and choose a role under Access role.
Three rules apply: you can't change your own access role, you can't change the role of an Owner, and only an Owner can assign the Owner role. New invitees get the default role; change it in Edit User afterwards if needed. For inviting and archiving members, see Users, roles, and MFA.
Who can do X?
The Who can… box above the Users list filters members by a single permission, for audits like "who can delete work items?".
Who can edit roles#
Editing roles requires the Manage Permissions permission (under Settings → Organization). Owner and the default Admin hold it. Treat it as a master key: a member with Manage Permissions and Manage Users can build a role with every permission and assign it to themselves. The only thing they still can't do is make anyone an Owner.
Changes take effect within seconds#
Changing a role, or a member's role, reaches them within seconds without a sign-out. If a change removes access to something they are viewing, it is removed from their screen and they are told why.
Permission reference#
Every permission as the matrix lists it, with its description and whether the Admin role, and the default Member role of a newly created organization, hold it. The Owner always has everything. "Admin override" means the permission reaches other members' content.
Module Access#
| Permission | Member | Admin |
|---|---|---|
| Map, Boards, Gantt, Automations, Items, Service Desk, Templates | yes | yes |
| Reports, Settings | no | yes |
| Plugin rows (one per installed plugin) | on | on |
Workstreams / Items#
| Permission | What it grants | Member | Admin |
|---|---|---|---|
| Create Items And Workstreams | Create new work items and workstreams. | yes | yes |
| Manage Own Items And Workstreams | Update, archive, and delete work items and workstreams where you have Owner-level sharing. | yes | yes |
| Manage All Items And Workstreams | Read, update, archive, and delete any work item or workstream, regardless of sharing. Admin override. | no | yes |
| Backdate Item History | Record an item's created date, creator, and status or board history as happening in the past, and correct them later. Requires Manage Own Items And Workstreams. See Correcting an item's real history. | no | yes |
Comments
| Permission | What it grants | Member | Admin |
|---|---|---|---|
| Create Comment | Post new comments on work items and workstreams. | yes | yes |
| Manage Own Comments | Edit and delete comments you authored. | yes | yes |
| Manage All Comments | Edit and delete other members' comments. Admin moderation override. | no | yes |
Time Entries
| Permission | What it grants | Member | Admin |
|---|---|---|---|
| Time Entry Access | On by default. Off removes every time-entry surface from the role. | on | on |
| Create Time Entries | Log time entries on work items. | yes | yes |
| Manage Own Time Entries | Edit and delete time entries you authored. | yes | yes |
| Manage All Time Entries | Edit and delete other members' time entries. Admin moderation override. | no | yes |
Boards#
| Permission | What it grants | Member | Admin |
|---|---|---|---|
| Create Board | Create new boards and board folders. | yes | yes |
| Manage Own Boards | Update, archive, and delete boards and folders where you have Owner-level sharing. | yes | yes |
| Manage All Boards | Read, update, archive, and delete any board or folder, regardless of sharing. Admin override. | no | yes |
Gantts#
| Permission | What it grants | Member | Admin |
|---|---|---|---|
| Create Gantt | Create new Gantts. | yes | yes |
| Manage Own Gantts | Update and delete Gantts you authored, including their initiatives, milestones, scenarios, and Gantt items. | yes | yes |
| Manage All Gantts | Update and delete other members' Gantts. Admin override. | no | yes |
Reports#
Viewing a report includes exporting it. None of these is granted to the default Member role.
| Permission | What it grants | Member | Admin |
|---|---|---|---|
| Read Report Current Progress | View the Current Progress report. | no | yes |
| Read Report Trending | View the Trending Progress, Burn Down, and Burn Up reports. | no | yes |
| Read Report Throughput | View the Throughput report (also unlocks the Service Desk Reports tab). | no | yes |
| Read Report Cumulative Flow | View the Cumulative Flow report. | no | yes |
| Read Report Churn | View the Churn report. | no | yes |
| Read Report Velocity | View the Velocity report. | no | yes |
| Read Report Cycle Time | View the Cycle Time report. | no | yes |
| Read Report Time Tracking | View the User Time Tracking and Time Allocation Matrix reports. Reports are organization-wide: they include time on items the viewer can't open. | no | yes |
Automations#
| Permission | What it grants | Member | Admin |
|---|---|---|---|
| Create Automation | Create new automations. | yes | yes |
| Manage Own Automations | Update, enable/disable, and delete automations you authored. | yes | yes |
| Manage All Automations | Update, enable/disable, and delete other members' automations. Admin override. | no | yes |
Service Desk#
| Permission | What it grants | Member | Admin |
|---|---|---|---|
| Send Public Replies | Send customer-visible replies on tickets. Without it a member can only add internal notes. | yes | yes |
| Manage Requesters | Create, edit, block, merge, and anonymize requesters and companies; open tickets for clients. | no | yes |
| Manage Service Desk Settings | Service desk enablement, inbound addresses and sending domains, SLA policies, schedules, portal branding, and request forms. Requires the Settings module. | no | yes |
Knowledge Base#
| Permission | What it grants | Member | Admin |
|---|---|---|---|
| Create Kb Articles | Create articles and edit your own unpublished drafts. | no | yes |
| Manage Own Kb Articles | Edit articles you authored, including after publication. | no | yes |
| Manage All Kb Articles | Edit any member's articles. Admin override. | no | yes |
| Publish Kb Articles | Publish, unpublish, and archive articles, edit slugs and audience, and manage the category tree. | no | yes |
| Comment On Kb Articles | Comment in article review threads; edit and delete your own article comments. | no | yes |
| Moderate Kb Article Comments | Delete, redact, resolve, and edit any member's article comments. Admin override. | no | yes |
| Manage Knowledge Base Settings | Knowledge Base settings, such as the stages a spec moves through. Requires the Settings module. | no | yes |
The descriptions above are the ones shown in the app. Manage Knowledge Base Settings opens Configure Settings → Knowledge Base, where the workspace's spec stages are set up; when it was added, admin roles and roles holding both Manage All Kb Articles and the Settings module were given it. One newer ability rides on an existing permission: Publish Kb Articles also approves or sends back proposed changes to published articles and moves articles into publishers-only stages. Likewise Manage All Kb Articles is what lets someone switch on a Spec Reached a Stage automation (see Specs and work items), and linking a spec to work items needs Create Kb Articles.
See Knowledge Base permissions for how these shape the module.
Saved Views#
| Permission | What it grants | Member | Admin |
|---|---|---|---|
| Create Stored View | Create new saved views. | yes | yes |
| Manage Own Stored Views | Update and delete saved views you authored (also needed to publish a view to portal customers). | yes | yes |
| Manage All Stored Views | Update and delete other members' saved views. Admin override. | no | yes |
Item Templates#
| Permission | What it grants | Member | Admin |
|---|---|---|---|
| Create Item Template | Create new templates. | yes | yes |
| Manage Own Item Templates | Update and delete templates you authored. | yes | yes |
| Manage All Item Templates | Update and delete other members' templates. Admin override. | no | yes |
API Keys#
| Permission | What it grants | Member | Admin |
|---|---|---|---|
| Create Api Key | Create API keys for yourself. | yes | yes |
| Manage Own Api Keys | Update and delete your own API keys. | yes | yes |
| Manage All Api Keys | View, update, and delete other members' API keys, for example to revoke a departed member's keys. Admin override. | no | yes |
| Manage Agent Claims | Take, renew, release and hand over agent work claims, and read who holds what. For teams whose AI agents coordinate through DevStride (see the agent work claims tools in the Tool Reference). Roles that held it when the Agents module arrived also received View Agents Module. | no | yes |
Agents#
| Permission | What it grants | Member | Admin |
|---|---|---|---|
| View Agents Module | See the Agents module: the Agent Fleet, its log, and the workflows your agents follow with what each step produced. The Owner and Admin roles hold it, and so does every role that already held Manage Agent Claims. Anyone with it can see the session details behind each Fleet row, including addresses. | no | yes |
AI Assistant#
| Permission | What it grants | Member | Admin |
|---|---|---|---|
| Use Ai Assistant | Open the AI Assistant and chat with it. Every role that existed when the assistant launched received it. | yes | yes |
| Manage Ai Assistant | Switch the assistant on or off, and choose which sources and models it may use; also opens Configure Settings → AI Assistants → Connect AI, the page for connecting an external AI client over MCP. Requires the Settings module. | no | yes |
| View Ai Usage | See AI Assistant usage and cost for the organization. Requires the Settings module. There is no usage page yet, so today it shows nothing. | no | yes |
See AI Assistant for what the assistant does and Settings, Permissions & Your Data for how to manage it.
Settings#
Every Settings permission requires the Settings module; the Data Model and Other groups additionally require Manage Org Configuration. The default Member role holds none of them. The groups below follow the Settings menu, and the Permissions page groups them the same way.
Organization
| Permission | What it grants | Admin |
|---|---|---|
| Manage Org Configuration | Edit the Organization Profile. It also opens two Admin pages, Global Automations and Formatting Rules. | yes |
| Manage Users | Browse, invite, change role and team assignment, and remove members. | yes |
| Manage Teams | Create, edit, and delete teams. | yes |
Data Model
| Permission | What it grants | Admin |
|---|---|---|
| Manage Labels | Create, edit, and delete labels (tags) and label groups. | yes |
| Manage Priorities | Create, edit, and delete priorities. | yes |
| Manage Fields | Manage custom fields: definitions, collections, and form groups. | yes |
| Manage Work Types | Create, edit, and archive item types, their statuses, and the estimate options assigned to them. | yes |
| Manage Workspace Tab Order | Reorder and toggle the tabs on each item type's detail page. | yes |
| Manage Sidebar Field Order | Reorder and toggle the sidebar fields on each item type's detail page. | yes |
Other
| Permission | What it grants | Admin |
|---|---|---|
| Manage Cadences | Create, edit, and archive cadences and time-boxes. | yes |
| Manage Import History | View, create, and run import jobs; see import history and templates. | yes |
Integrations
| Permission | What it grants | Admin |
|---|---|---|
| Manage Integrations | Install, configure, and remove integrations. | yes |
| Manage Database Credentials | Generate, activate, revoke, rotate, and delete read-only database credentials. | yes |
| Manage Identity Providers | Configure, verify, and remove SAML/OIDC identity providers and their email domains. | yes |
| Manage Webhooks | Register outbound webhook endpoints, choose their events, rotate their secrets, read the delivery log and replay deliveries. Not part of any permission template. | yes |
Subscription
| Permission | What it grants | Admin |
|---|---|---|
| Manage Subscription Tier | View the workspace's plan and enrol in monthly card payments. | yes |
| Manage Billing Details | View and edit billing contact and address details. | yes |
| Manage Payment Method | View and update the payment method on file. | yes |
| Manage Billing History | View past invoices and billing history. | yes |
Admin
| Permission | What it grants | Admin |
|---|---|---|
| Manage Permissions | Create, edit, and delete roles and their permissions. Cannot assign the Owner role. | yes |
| Manage Lock Settings | Configure Time Tracking: enablement, period type, grace window, and per-period overrides. | yes |
| Manage Training Sandboxes | View and manage the organization's training sandboxes. | yes |
| View Authentication Log | See who signed in to the organization, how they signed in, and sign-in problems reported by the browser (Authentication Log). Part of no template, because the log shows members' network addresses: grant it on its own. Roles that held Manage Permissions when it was introduced were given it. | yes |
Four permissions worth guarding
Manage Permissions lets a holder give themselves anything. Manage Database Credentials hands out a database login to production data. Manage Identity Providers controls who can sign in as whom. Manage Webhooks can send every item and comment in the organization, internal notes included, to any public URL. The default Admin holds all four; think before adding them to a custom role.
How roles relate to sharing#
Roles decide the kinds of action you can take; Sharing & Access decides which objects you can take them on. For items, workstreams, boards, and folders both are checked. Understanding Permissions walks through how they combine.