Every member holds exactly one role. The role decides what they can do anywhere in DevStride: which modules appear in their navigation, and whether they can create, edit their own, or manage everyone's items, boards, Gantts, reports, automations, time entries, API keys, and settings.
Every organization starts with three roles:
During onboarding you normally only need two moves: set your fellow administrators to Admin on the Users page, and leave the default role for new members as Member. Custom roles ("Reviewer", "Contractor", "Finance") come later, once you know which areas you want to open or close for a group.
How to build a role, apply a permission template, set the default role for new members, and assign roles is covered on Roles & Permissions.
Understanding Permissions
Orientation for new admins: DevStride controls access with two layers — roles (what a person can do anywhere) and sharing (what they can open) — and where to go to set each.
Sharing & Access
Orientation for new admins: sharing grants Viewer, Commenter, Editor, or Owner access to one workstream, item, board, or folder, and children inherit their parent's sharing.