Sharing answers "who can open and change this specific thing?". It is the per-object half of DevStride's access model; the other half is your role. Use sharing to open one board to a single team, keep a workstream private until it is ready, or give the whole organization read access to a plan, all without touching anyone's role.
Sharing applies to work items, workstreams, boards, and board folders. Item templates and knowledge-base articles have sharing dialogs of their own (see Templates and Sharing articles and categories). Gantts, reports, automations, saved views, API keys, and settings have no per-object sharing; your role alone decides.
| Level | Items and workstreams | Boards and folders |
|---|---|---|
| Viewer | Only view | Only view |
| Commenter | View, comment | not offered |
| Editor | View, comment, edit | View, edit |
| Owner | Everything, including archiving, deleting, and transferring ownership | Same |
Two states you will see but can't choose directly:
Your role still has to allow the action. Being an Editor lets you edit only if your role includes Manage Own Items And Workstreams (or Manage Own Boards); see Understanding Permissions.
The dialog is titled Manage Permissions (boards add the board's name) and has three sections: User Access, Team Access, and Organization Access.
When more than one grant applies to the same person, the most specific wins: a User Access row beats a Team Access row, which beats the Organization row. Remove Access on a user is an explicit block, so you can share a workstream with a whole team and still exclude one of its members.
Choose Transfer Ownership on a user's row to make them the owner. Only the current owner can do this (for boards, anyone with Manage All Boards can too). You keep Editor access afterwards.
New objects inherit their parent's sharing: an item inherits its workstream, a board inherits its folder. A new top-level object with no parent starts private, with you as its only owner. You can override any row on the child; the custom setting replaces the inherited one for that row.
Filtered lists only contain objects you can read. A workstream appears in a filtered Map or Items list only when an item you have access to matches, so a restricted member can see a shorter list than a colleague. Details: What you see in filtered lists.
It isn't a sharing setting; it is their role. Manage All Items And Workstreams and Manage All Boards intentionally bypass per-object sharing so administrators can manage everything. The Owner and the default Admin role hold them. See Understanding Permissions.
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.
My Work
How the shared Filters, Sort, Options, and Views toolbar works across DevStride, and which filters the My Work list offers.