Permissions

Understanding Permissions

How roles and sharing combine to decide what each person can see and do, why the Owner role is special, and three common setups you can copy.

Two systems decide what a person can do in DevStride. Keep them apart in your head and everything else in this section follows.

RolesSharing
Question it answersWhat kind of thing can this person do?Which specific things can they reach?
ScopeThe whole organizationOne item, workstream, board, or folder (and whatever inherits from it)
Set whereConfigure Settings → Admin → PermissionsThe Manage Permissions dialog on the object
Example"Can create boards", "Can view the Velocity report""Alex is an Editor on the Marketing workstream"

Roles grant capabilities. Sharing scopes objects.

Think of it as hiring an electrician and handing out keys. Being an electrician (the role) means you are allowed to do electrical work anywhere, but it gets you into no building on its own. A key (sharing) opens one building, but holding a key doesn't make you an electrician. To rewire a room you need both.

How the two combine

  • Seeing an item, workstream, board, or folder is decided by sharing alone. A role never hands out individual objects (with one exception, the "Manage All" overrides below).
  • Changing one needs both. Your role must include the capability (for example Manage Own Items And Workstreams) and your sharing level on that object must be high enough: Editor to edit, Owner to archive or delete. The more restrictive of the two wins.
  • Some things have no sharing at all: Gantts, reports, automations, saved views, API keys, and settings. Your role alone decides, and anything you create there is "yours" because you authored it.

Objects that carry sharing: work items, workstreams, boards and board folders, item templates, and knowledge-base articles and categories.

Module Access is navigation, not capability

Every role has two parts. Module Access decides which modules appear in the sidebar (Map, Boards, Gantt, Reports, Automations, Items, Settings, Service Desk, Templates, and each installed plugin). Permissions decide what the person can actually do. Hiding the Boards module from a role removes the menu entry and blocks the route; it does not stop that person seeing an item's board placement, or using the API. Use Module Access to declutter, and Permissions to restrict.

"Manage All" overrides see past sharing

Two permissions are deliberate exceptions to "sharing decides what you see":

  • Manage All Items And Workstreams: read, update, archive, and delete any work item or workstream, whether or not it was shared with you.
  • Manage All Boards: the same for every board and board folder.

The other Manage All … permissions (Gantts, Automations, Saved Views, Item Templates, API Keys, Comments, Time Entries, knowledge-base articles) let a role act on things other members authored. None of them is granted by default to the Member role; the default Admin role holds every one. This is why an administrator can see a workstream nobody shared with them: it is their role, not a sharing setting.

The Owner role is always all-access

Every organization has exactly one Owner role. It is locked: it can't be renamed, edited, or deleted, and it passes every permission check without consulting a list. At least one active member must always hold it, and only a current Owner can make another member an Owner. An Owner who wants to leave promotes someone else first; the system refuses to remove the last Owner.

The default Admin role holds every permission there is, so in day-to-day capability it matches the Owner. The difference is lineage: only an Owner can create another Owner.

Changes take effect within seconds

Role edits, role reassignments, and sharing changes reach affected people within seconds, with no sign-out. If a change removes access to something someone is looking at, it disappears from their view and they are told why.

Three common setups

A contractor who should see one workstream only

  1. In Configure Settings → Admin → Permissions, click New Role, name it Contractor, and switch on only what they need: Module Access for Items (and Boards if they work from a board), and under Workstreams / Items the permissions Create Items And Workstreams, Manage Own Items And Workstreams, Create Comment, Manage Own Comments, and the time-entry pair if they log time. Leave every Manage All … permission off.
  2. Invite them from Configure Settings → Users, then open Edit User and set their Access role to Contractor.
  3. Open the workstream, click its sharing icon, and under User Access add them as Editor (or Viewer). Leave the Organization row as it is.

They now see that workstream and its items, and nothing else: My Work, Items, and search only show what is shared with them. See Sharing & Access.

A read-only stakeholder

  1. Create a role named Stakeholder. Turn on the modules they should browse (Map, Boards, Gantt, Reports) and, if they should see analytics, the Read Report … permissions. Leave Create Items And Workstreams off: without it the role can't edit, comment, or log time anywhere, whatever is shared with them.
  2. Optionally switch Time Entry Access off to hide logged time from them everywhere.
  3. Share what they should see as Viewer: either add them (or their team) to the top-level workstreams and boards, or set the Organization row on those objects to Viewer so every member can read them.

A team lead who manages their own board

The default Member role already includes Create Board and Manage Own Boards, so no role change is needed:

  1. Open the board's menu and choose Permissions.
  2. Add the lead under User Access, then set their level to Transfer Ownership (only the board's current owner can do this). As owner they can edit, archive, and manage who else has access; you keep Editor access.

If one person should manage every board, grant their role Manage All Boards instead of transferring boards one at a time.

Where to go next