Two systems decide what a person can do in DevStride. Keep them apart in your head and everything else in this section follows.
| Roles | Sharing | |
|---|---|---|
| Question it answers | What kind of thing can this person do? | Which specific things can they reach? |
| Scope | The whole organization | One item, workstream, board, or folder (and whatever inherits from it) |
| Set where | Configure Settings → Admin → Permissions | The 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.
Objects that carry sharing: work items, workstreams, boards and board folders, item templates, and knowledge-base articles and categories.
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.
Two permissions are deliberate exceptions to "sharing decides what you see":
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.
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.
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.
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.
The default Member role already includes Create Board and Manage Own Boards, so no role change is needed:
If one person should manage every board, grant their role Manage All Boards instead of transferring boards one at a time.
Authentication Log
See who signed in to your organization, how and from where, which Google, Microsoft and single sign-on names are linked to each member, and why company single sign-on was refused.
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.