Configure Settings → Organization → Users is where you manage the people in your organization: who is a member, what access role each one holds, and what to do when someone is locked out. The page needs the Manage users permission (default Owner and Admin roles, or any role given the Manage people template).
Every member holds exactly one access role. Each organization starts with three:
| Role | What it is for |
|---|---|
| Owner | Full authority over everything, including resetting any member's password or MFA. There is exactly one Owner role; it cannot be renamed, edited or deleted. |
| Admin | Manages people, settings and content. Starts with every grantable permission and is fully editable. |
| Member | The standard contributor: works items, boards, Gantts, automations, saved views and templates, and manages their own API keys. No access to Settings or reports by default. |
Admin and Member are starting points, and you can add custom roles. What each role can do is configured on Configure Settings → Admin → Permissions; this page only assigns roles to people. See Roles & Permissions for the catalog of permissions and Understanding Permissions for how roles combine with per-object sharing. Roles are per organization: the same person can be an Admin in one organization and a Member in another.
The table is read-only; you act on a member from the pencil (Edit User) or the red X (Archive User) at the end of their row.
| Column | Shows |
|---|---|
| User | Name and avatar |
| Sign-in address | |
| Status | Active, Invited, Inactive, or a pending join request. A red Email failed marker means the invitation email did not send. |
| Deactivated Date | When an inactive member was archived (shown with Show Inactive) |
| Access role | The role they hold |
| Labels | User labels (see below) |
| Personas | The personas they can fill |
Controls above the table:
Each invitee appears immediately with the Invited status and starts as a Member; open their row and change the Access role if they need more. They accept by following the email, or simply by signing in with a Google or Microsoft account whose address matches (see below). Click Resend invite in the Edit User dialog if they cannot find the email.
If an address belongs to a member you previously archived, DevStride stops and asks:
Previously Archived User — You are inviting a previously archived user (name — email). Would you like to re-enable this user?
Re-enable User reactivates their existing membership with its history and emails them to say their account is back. Cancel changes nothing. Every reinstatement, from this prompt or from Reinstate in the Edit User dialog, emails the member.
A failed send is shown, not hidden: the row reads Invited with a red Email failed marker and the tooltip "The invitation email failed to send. Edit the user to resend it." Open the member and click Resend invite; a successful resend clears the marker.
Click the pencil on a row. Everything about the member is in one dialog; change what you need and click Update User.
| Section | What you can do |
|---|---|
| Identity (read-only) | Username, email, phone, timezone, and the dates they joined and were reinstated. |
| Membership | Change the Access role; select and order Personas; add or remove Labels. |
| Status | Reinstate an inactive member, Resend invite to an invitee, or Accept / Decline a request to join your organization. |
| Security | The member's Password age with a Reset button, and their MFA status (Enabled / Not Enabled) with a Reset button. |
| Permissions (read-only) | Exactly what the member's role grants, grouped by area. |
Create the personas first in Configure Settings → Organization → Personas (see Personas). Then open the member, tick their Personas, and use Move up / Move down to order them. The first active persona is the fallback used when an assignment has no persona selected, so put their usual persona first. Click Update User.
Removing a persona from a member clears them from current assignments that need that persona, leaving the work waiting for someone who can fill it. Time already recorded keeps the persona it was captured with. Personas never change what a member can read or edit.
Labels are free-form tags on people, grouped into label groups (for example a Location group with Austin and Remote). Use them to filter the Users table, to build User Picker custom fields whose options are "everyone with this label" (User options by group → User Labels on the field), and to group and filter the User Time Tracking report by a reporting team such as Home Team. Create groups and labels from the Labels section of the Edit User dialog (Manage User Labels → New Label Group: a group name plus comma-separated labels), then tick the labels each member should carry.
Click the red X on a row (Archive User) to remove someone from the organization. Their items, comments and time stay; they lose access, and any API keys they created stop authorizing requests against the organization. Archived members show under Show Inactive, where Reinstate brings them back.
Members can sign in with a Google account or a personal Microsoft account using the provider buttons on the login page. There is nothing to configure per member: DevStride matches the account to the member by email address.
Work and school Microsoft accounts are handled by Enterprise SSO, which also offers a Require single sign-on login policy on the Identity Providers page.
When someone loses their authenticator or phone, an Admin or Owner clears their MFA so they can sign in with their password alone and enrol again.
A reset removes MFA entirely; it does not choose a new method for the member. They set MFA up again themselves from My Account → User Profile (see below).
Use this when a member has forgotten their password or you suspect the account is compromised, and especially when they cannot receive email. DevStride issues a temporary password, shows it to you once, and makes the member choose a new one at their next sign-in.
The member signs in with the temporary password and is taken straight to a choose a new password screen; the temporary password stops working once they do. No email is involved, which is what lets you help someone whose mailbox is the problem. If existing sessions could not be signed out, the dialog says so; for a compromised account, contact support to force them out.
A member who has never finished signing up (invited but not yet accepted) has no password to reset; Resend invite instead.
Any member can reset their own password from the sign-in page with Forgot password?: enter your email, then the code DevStride emails you (from no-reply@devstride.com) along with your new password. Ask an Admin or Owner for a reset only when you cannot receive that email. There is no separate change-password screen inside the app.
You have 3 minutes to enter the code after signing in. Past that, the sign-in page tells you That code has expired. Please sign in again to get a new code. and returns you to the form with your password still filled in: click Sign in again and a fresh code is sent. A mistyped code within the 3 minutes says Verification code invalid and lets you try again.
Only you can enrol your own MFA. An administrator's reset clears the lockout; you choose and set up the new method.