Before you invite the wider team, it helps to know that DevStride checks access in two layers, and you configure them in two different places.
| Layer | Question it answers | Where you set it |
|---|---|---|
| Role | What is this person allowed to do across the organization — create boards, see reports, change settings? | Configure Settings → Admin → Permissions |
| Sharing | Which specific workstreams, items, boards, and folders can they open? | The Manage Permissions dialog on the object itself |
Think of the role as the kind of key someone holds and sharing as the list of rooms that key opens. You need both: a Member who is shared into a board can work on it, but still cannot open Reports if their role does not allow it. Administrators see everything not because of sharing but because the default Admin role carries "Manage all…" overrides.
For onboarding, the usual order is: give your co-admins the Admin role on the Users page, leave everyone else as Member, and only then start restricting individual workstreams or boards.
The full model, with worked examples, is on Understanding Permissions. Then see Roles & Permissions and Sharing & Access.
The AI Assistant
Orientation for new admins: switch on the AI Assistant so members can ask how-to questions and work their items by chat, and decide what it may use.
Roles & Permissions
Orientation for new admins: every member holds one role (Owner, Admin, Member, or a custom role) that decides what they can do organization-wide; build and assign roles in Configure Settings → Admin → Permissions.