Permissions

Sharing & Access

Grant people and teams access to individual items, workstreams, boards, and folders with the Manage Permissions dialog, and understand levels, inheritance, and ownership.

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.

Access levels

LevelItems and workstreamsBoards and folders
ViewerOnly viewOnly view
CommenterView, commentnot offered
EditorView, comment, editView, edit
OwnerEverything, including archiving, deleting, and transferring ownershipSame

Two states you will see but can't choose directly:

  • Inherited Owner: ownership that comes from a parent (an item's workstream, a board's folder). It can't be changed on the child.
  • Restricted: shown on the Organization row when the organization as a whole has no access, so only the listed users and teams can reach the object.

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.

Open the Manage Permissions dialog

  • Items and workstreams: click the sharing status icon next to the title in the item drawer. Its tooltip reads Share and Manage Permissions, or View Permissions when you can only look.
  • Boards and folders: open the board or folder menu and choose Permissions. You need edit access to the board to change its sharing.

The dialog is titled Manage Permissions (boards add the board's name) and has three sections: User Access, Team Access, and Organization Access.

Grant, change, and remove access

  1. Type in Search for users or teams..., pick a person or team, choose a level (the default is Viewer), and click Add.
  2. Change an existing grant with the level selector on its row. The selector also offers Remove Access, and, if you are the owner, Transfer Ownership.
  3. On the Organization row, choose a level to give every member a baseline, or Remove Access to make the object Restricted to the people and teams listed above.
  4. Click Done to close.

How grants layer

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.

Transfer ownership

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.

Inheritance

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.

What you see in lists

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.

Why an administrator can see things you didn't share

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.

Object-specific details