More on Permissions

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.

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:

  • Owner — unrestricted; exactly one per organization and it cannot be edited.
  • Admin — manages people, settings, and all content (includes the "Manage all…" overrides).
  • Member — the default for new invitees; works on content shared with them but cannot change organization settings.

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.