Workspace access in Reqflo is controlled through a small set of roles that apply across all journeys in the workspace. Roles determine whether someone can manage workspace settings, edit journeys, or only view them.
When to use it
Go to Admin → Users and access when you need to:
- Invite a new teammate to the workspace.
- Promote a viewer to editor so they can make changes to journeys.
- Transfer ownership or grant another owner for administrative redundancy.
- Remove a user who has left the team.
Key concepts
Workspace roles vs. journey roles. Workspace roles set the baseline for what a user can do across all journeys. Individual journeys can also have their own access configuration (owners and editors per journey), which can be more restrictive than the workspace default. See Journeys: access for per-journey controls.
The three workspace roles:
| Role | What they can do |
|---|
| Owner | Full workspace administration — manage users, secrets, environments, runners, and all journey settings. |
| Editor | Create and edit journeys, run them, and configure values and cases. Cannot change workspace-level admin settings. |
| Viewer | Inspect journeys, view run results, and use Runbooks. Cannot modify journeys or workspace configuration. |
Viewers can still be granted editor or owner access on specific journeys — workspace role is a floor, not a ceiling.
How it works
Users are invited by email. When they accept, they are assigned the role selected at invite time. You can change a user’s role at any time from the Users and access page.
Ownership transfers are immediate — the outgoing owner retains their role only if explicitly kept as an owner afterward. Workspaces must always have at least one owner.
Examples
Inviting an editor.
Open Admin → Users and access, enter the user’s email, select Editor, and send the invite. The user receives an email and joins the workspace on acceptance.
Upgrading a viewer to editor.
Find the user in the list, open their role dropdown, and select Editor. The change takes effect immediately — no re-invite needed.
Restricting a sensitive journey further.
Even after granting workspace editor access, you can mark a specific journey Private and limit its editor list. See Private journeys and Journeys: access.
Related pages
