Search documentation

Search BriefFlow's documentation by page title, section heading, or content.

What this does

The Users page is where the team is managed: inviting people, changing roles, and disabling or re-enabling accounts.

Before you begin

Managing users requires the users.manage permission (Administrators by default).

Inviting someone

Administrator permission required

Requires the users.manage permission.
The Users page — team members, roles, and status at a glance.
  1. Open Users in the sidebar.
  2. Select Invite User.
  3. Enter their full name and email.
  4. Choose their role — Administrator, Developer, or Tester.
  5. Optionally add a job title.
  6. Select Send Invitation.
The Invite User dialog.

They receive a branded email with a link to accept the invitation and set their own password — you never set or see anyone else's password.

Managing a pending invitation

A pending invitation can be resent (if it expired or the email was missed) or revoked (if it was sent in error, or the person shouldn't join after all) at any time before it's accepted, from the same row on the Users page.

Changing a role

  1. Open the person's row on the Users page.
  2. Change their role.
  3. Confirm.

Their available navigation and permissions update immediately on their next action.

Disabling and re-enabling an account

  1. Open the person's row on the Users page.
  2. Select Disable (or Enable to reverse it later).

Disabling an account blocks sign-in without deleting the person's history — their past comments, understanding submissions, and QA results remain intact and attributed to them, since that history is part of the team's real record. Nothing is lost between disabling and re-enabling.

Note

The last remaining Administrator account can't be disabled — BriefFlow always keeps at least one administrator able to sign in.

Common issues

I can't disable this account. It's the workspace's only remaining Administrator — promote someone else first.

The invitation email never arrived. Check the address for typos, then use Resend rather than sending a duplicate invitation.