Skip to content
FRA Flow
Menu
SoftwareBS 9792AppPricingAssessorsToolsDocs
Try FRA Flow freeTalk to usLog in

Users and roles

How to invite people to your FRA Flow workspace and assign assessor, reviewer, or admin roles from the Team & roles page.

By Richard Pryce·Last updated

FRA Flow has three roles: assessor, reviewer, and admin. Most practices have everyone as an assessor + reviewer, with a specific person also holding admin for billing and invitations. This page is the short reference for inviting people and managing their roles.

The three roles

  • Assessor does site visits and writes draft reports. Assessors see the workbench, capture observations, generate drafts, and submit drafts for review. They do not see the reviewer queue page.
  • Reviewer signs off draft reports. Reviewers see the reviewer queue, can open any draft in the tenant, edit paragraphs, and approve or reject the draft. Reviewers can also do assessor work; the role is additive.
  • Admin runs the workspace. Admins manage invitations, billing, branding profiles, and the assessment list across all assessors. Admin is additive too; an admin who is also an assessor sees both surfaces.

A senior assessor in a small consultancy typically holds all three roles. A larger practice typically has admin scoped to one or two people, reviewer scoped to senior assessors, and assessor for everyone else.

Inviting a teammate

Open Settings → Team & roles. The top card is the invite form. Enter the teammate's email and click Send invite. We email them an invite link; they click it, sign up, and land in the workspace.

New teammates start with no FRA Flow role. They can sign in but every section of the app gates on at least one role, so the first thing to do after they accept is open the same page and assign their roles from the table below the invite form.

Changing a teammate's roles

The People in this workspace card lists everyone in the tenant with one column per role. Each cell is a circular toggle: tap to grant the role (filled blue with a check), tap again to revoke it (empty white with a slate dot). Changes take effect on the user's next page load.

Pre-pilot you cannot remove the last admin from the workspace yet (the underlying server action does not block this). If you need to hand admin off, invite the new admin first, grant them the role, then revoke admin from the previous holder.

Removing a teammate

Removal from the workspace is not yet a button on the Team & roles page. Pre-pilot, ask Richard or remove them from the underlying Clerk organisation; their historical attributions on signed reports stay intact (the audit trail does not collapse around removed users).

A self-serve Remove action lands alongside the M3 audit hardening pass.

Single sign-on (SSO)

Enterprise tier supports SSO via standard providers (Okta, Microsoft Entra, Google Workspace). Configuration sits under Settings → Identity once your workspace is on the Enterprise tier; pre-pilot tiers use email + the Clerk-managed sign-in flow.

Pre-pilot caveats

  • The Team & roles page covers invite + role assignment. Bulk import, SSO group → role mapping, and self-serve user removal are post-pilot.
  • The user list shows tenant members; cross-tenant directory features (e.g. inviting a contractor who does work for two separate landlords) are post-pilot.

Where to go next

Next

Branding →