Organization

Users, Roles & MFA

Invite and manage organization members, understand the Owner, Admin, and Member roles, sign in with Google or Microsoft, edit a member from the Edit User dialog, reset a user's password or multi-factor authentication, and change your own password.

Overview

Your organization's people and their access are managed under Settings → Organization → Users. From here you can review every member, edit who they are and what they can do, and—when someone is locked out—reset their password or their multi-factor authentication (MFA).

This page covers:

The roles that govern what members can do (Owner, Admin, Member, plus any custom roles)
Where to find and review users in your organization
Editing a member from the Edit User dialog
How an Admin or Owner resets a user's password or MFA
How anyone changes their own password

Roles

Every member holds exactly one role, which determines what they can do across the organization. Each organization starts with three:

Owner — full, unrestricted access to everything, including the ability to reset the password or MFA for any member (including other Owners). There is exactly one Owner role per organization, and it can't be renamed, retuned, or deleted, so administration is never locked out.
Admin — manages organization settings, people, and content, including resetting the password and MFA for Members and other Admins.
Member — a standard contributor without organization-administration privileges.

Roles are now customizable

Admin and Member are editable starting points, not fixed presets — you can retune what each one can do, and you can create your own custom roles. What a role can do is configured in Configure Settings → Permissions. For the full model, see Roles & Permissions and Understanding Permissions.

Roles are scoped to the organization

Role-based permissions are enforced per organization. The actions described below depend on the role you hold in the organization you're currently working in.

Signing in with Google or Microsoft

Members can sign in with their Google account or personal Microsoft account (outlook.com, hotmail.com, live.com, or any address registered as a Microsoft account) instead of a password, 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:

A member whose email matches their Google or Microsoft account can sign in with that button right away; the first sign-in links the two, and every sign-in method keeps working. One member can link both.
An invited member can accept their invitation by signing in with either provider — no password setup required. Their account is activated exactly as if they had completed the invitation email.
An account that doesn't match any member is refused: the visitor is told the account isn't linked and to ask their administrator for an invitation. No account is ever created from an unmatched sign-in.

Work and school Microsoft accounts are served by Enterprise SSO instead — the Microsoft button is for personal accounts.

Organizations that require MFA

If your organization requires multi-factor authentication, members of that organization can't use Google or Microsoft sign-in — those sign-ins don't pass through DevStride's MFA challenge, so allowing them would bypass the requirement. Those members continue to sign in with their password and MFA as before.

The same rule applies to Enterprise SSO: an organization that requires MFA can't use it either. If you want SSO, enforce multi-factor authentication at your identity provider instead.

Viewing Users

In the left sidebar, click Settings to expand the settings menu.
Click Organization, then select Users.
The organization user table lists every member — their name, email, status, role, and labels. The table is read-only: it's for scanning your organization at a glance, not editing in place.
Each row ends with two actions: a pencil to edit the member, and a red ✕ to archive them.

The "who can…" permission filter

At the top of the Users screen, the Who can… filter answers audit questions like "who can delete work items?" or "who can manage billing?". Pick an atomic permission and the table narrows to members whose role grants it (Owners always match, since they can do everything).

The permission list is grouped and ordered exactly like Configure Settings → Permissions — Module Access first, then each capability area, with Comments, Time Entries, and the Settings sub-groups nested underneath — so you can find the permission you have in mind in the same place you'd look for it there.

Editing a Member — the Edit User Dialog

Click the pencil on a member's row to open the Edit User dialog. Everything about a member lives here, in one place:

Identity (read-only) — username, email, phone, timezone, and the dates they joined and were reinstated.
Membership — change their Role, and add or remove Labels.
Status — depending on where the member is in their lifecycle, act on it here: Reinstate an inactive member, Resend invite to someone who hasn't accepted, or Accept / Decline a pending join request.
Security — the member's Password age with a Reset action, and their MFA status with a Reset action. See Resetting a User's Password and Resetting a User's MFA below.
Permissions — a read-only summary of exactly what the member's role grants.

Change what you need and click Update User to save; the row updates to match.

You can't lock yourself out

Some edits are deliberately blocked to keep administration safe: you can't change your own role, and an Admin who isn't an Owner can't change the role, labels, password, or MFA of an Owner. Where an action isn't allowed, its control is hidden or disabled.

Inviting Users

Invite people from Settings → Organization → Users with Invite Users. Enter their email addresses, choose the role they'll hold, and send. Each invitee appears in the table right away with an Invited status until they accept.

Inviting someone you archived before

If an email you're inviting belongs to a member you previously archived (removed from the organization), DevStride stops and asks rather than quietly doing nothing:

Previously Archived User — You are inviting a previously archived user (name — email). Would you like to re-enable this user?

Choose Re-enable User and their existing membership is reactivated — they keep their history, and they're emailed to let them know their account is back. Choose Cancel and nothing happens to them.

Anyone reinstated is now told

Every reinstatement emails the member — whether it came from this prompt or from the Reinstate action on an archived user's row. Previously an account could come back to life without the person ever being told.

When an invitation email doesn't arrive

Invitation emails can fail to send — a typo'd address, a bouncing domain, a mail provider rejecting the message. That failure is now visible instead of silent: the member's row shows a red Email failed marker next to their Invited status, with the tooltip "The invitation email failed to send. Use Resend to try again."

Click Resend on that row to try again. A successful resend clears the marker.

Check here first when someone says they never got the invite

If the row shows Invited with no failure marker, the email left DevStride successfully — so the next place to look is the recipient's spam folder or their organization's mail filtering, not DevStride.

Resetting a User's MFA

When a user loses access to their authenticator device or phone, an Admin or Owner can clear their MFA. After a reset, the user is no longer prompted for an MFA code at login and can set MFA up again themselves.

Who can reset MFA

Both Admins and Owners can reset MFA for users in their organization.
A reset is only possible for a member who currently has MFA enabled. If a member's MFA status is Not Enabled, there's nothing to reset and no Reset button appears.

Owners are protected

An Admin who is not an Owner cannot reset MFA for an Owner. The Reset button is hidden in that case, and the action is blocked with the message "You cannot reset MFA for an owner." Only an Owner can reset another Owner's MFA. This protection now spans every organization the Owner belongs to — you can't strip the MFA of someone who is an Owner elsewhere but only a plain member of your organization.

How to reset

Open Settings → Organization → Users.
Find the member and click the pencil on their row to open the Edit User dialog.
In the Security section, find the MFA row and confirm it reads Enabled. A red outlined Reset button appears next to it.
Click Reset. A confirmation dialog titled Reset MFA asks, "Reset MFA for ?"
Click the red Reset MFA button to confirm.

On success, you'll see the message: "MFA has been reset for ." If the reset fails, an error message asks you to try again and to contact support if the problem persists.

A reset clears MFA—it doesn't set a new method

Resetting MFA removes it entirely. It does not choose or re-issue a method on the user's behalf. After a reset, the affected user must set up MFA again themselves the next time they need it.

Resetting a User's Password

When a member is locked out — they've forgotten their password, or their account may be compromised — an Admin or Owner can reset it for them directly, without waiting on an email. DevStride issues a temporary password, shows it to you once, and requires the member to choose a new one the first time they sign in with it.

Who can reset a password

Both Admins and Owners can reset the password of members in their organization.
An Admin who is not an Owner cannot reset an Owner's password (the same cross-organization protection as MFA), and the Reset button is hidden.
A member who hasn't finished signing up (an invited or imported user who has never set a password) has no password to reset. The button is hidden, and if the action is attempted anyway DevStride explains that they should be re-invited instead.

How to reset

Open Settings → Organization → Users and click the pencil on the member's row.
In the Edit User dialog's Security section, click Reset on the Password row.
Confirm the prompt — it explains that the member's current password stops working immediately, that DevStride will try to sign them out of existing sessions, and that you'll be handed a temporary password to pass on.
A Temporary password dialog appears with the generated password and a Copy button.

The temporary password is shown only once

It is never stored and can't be retrieved again. Copy it and hand it to the member securely (in person, over the phone, or through a trusted channel). If you lose it, just reset the password again — that issues a fresh one.

What the member does next

The member signs in with the temporary password and is immediately taken to a "choose a new password" screen — they can't reach the app until they set a real password of their own. Once they do, the temporary password stops working.

No email is involved

Unlike the self-service Forgot Password flow below, an admin reset never emails the member. The credential travels through you, which is what lets you help someone whose email access is itself the problem.

If sessions couldn't be signed out

A reset always changes the password, and DevStride also tries to sign the member out of any sessions they already have open. If that sign-out couldn't be completed, the Temporary password dialog says so — any already-signed-in session may stay active until it expires. If you were resetting because the account was compromised, contact support to force those sessions out.

Changing Your Own Password

Any member can reset their own password from the sign-in screen — you don't need an administrator for this.

On the Sign in page, click Forgot password?.
Enter your email address and submit. If an account exists for that email, DevStride emails you a 6-digit code.
Enter the code along with your new password and confirm it.
Sign in with the new password.

Which path should I use?

Use Forgot password? to reset your own password by email. Ask an Admin or Owner for a reset when you can't receive the email — for example if you've lost access to the mailbox itself. There is no separate "change my password" screen inside the app; the Forgot Password flow is the self-service path.

Setting Up MFA Again

After their MFA has been reset, a user can re-enroll from their own account using the Setup Multi Factor Authentication dialog. Two methods are supported:

Auth App (recommended) — use an authenticator app such as Google Authenticator or Microsoft Authenticator to get auto-generated codes.
Text Message — receive a verification code by SMS.

Self-service re-enrollment

Only the user can re-enroll their own MFA. An Admin or Owner reset clears the lockout; the user chooses and sets up the new method themselves.

Org Profile — configure your organization's name, domain, timezone, and other profile details.
Roles & Permissions — define what each role can do, in Configure Settings → Permissions.
Understanding Permissions — how roles and per-object sharing combine.
Workstream & Item Permissions — the object-level access these roles underpin for workstreams and items.
Board & Folder Permissions — the object-level access these roles underpin for boards and folders.

Org Configuration

Set up your organization's profile, logo, and workflow automation, and navigate the reorganized Settings area.

Cadences