Flow.Documentation

Roles, teams and rights

8 steps± 6 minVideoVerified 27 Oct 2026
  1. Step 1 · Open People
  2. Step 2 · Give someone a role
  3. Step 3 · What does a team member see?
  4. Step 4 · The built-in roles
  5. Step 5 · Create a team
  6. Step 6 · Members, a role and a duty
  7. Step 7 · Rights: who may do what, and why
  8. Step 8 · Roles for decisions: who decides what

In Governance a role sets what someone sees and may do: Owner, Board, Project lead, Team member, Auditor or Client reader. You give someone a role, or you put people in a team that holds roles and duties. The Rights page shows per person and per part what they may do, and where that right comes from.

Watch the whole guide as a video8 steps in one film
Step 1 / 8

Open People

People lists everyone in your organisation who uses Governance: their role, their teams and what they decide as. Members appear here by themselves once they sign in for the first time; whoever leaves the organisation disappears again.

  1. Click People
Open People · Click People
  1. Click People
Open People · Click People
Open People · Tom is in the list, without a role yet.
Step 2 / 8

Give someone a role

Choose the role in the Role column. It is saved at once; the message lets you undo it. As the organisation's owner in the portal you are always Owner, even without a role here.

  1. In Role of Tom Fisher, choose Team member
Give someone a role · In Role of Tom Fisher, choose Team member
Give someone a role · A message: Tom Fisher is now Team member, with Undo.
Step 3 / 8

What does a team member see?

Click someone's name: the inspector on the right says per part what that person can do, and why. A team member views projects and the governance profile and writes their own hours, but sees no quotes, no people and no decision ledger. My work only shows what is theirs.

  1. Click Tom Fisher
What does a team member see? · Click Tom Fisher
What does a team member see? · Projects and Stage and Governance profile: View, as Team member. The rest: no right.
Step 4 / 8

The built-in roles

Under the list are the six roles, one sentence each. Owner may do everything. Board manages quotes and projects. Project lead edits them and approves hours. Auditor reads everything and exports the decision ledger. Client reader is a client who only follows the Stage of their own project.

The built-in roles · Six cards: Owner, Board, Project lead, Team member, Auditor and Client reader.
Step 5 / 8

Create a team

With a team you give several people the same roles and duties at once, for example everyone who reviews changes on security. Open Teams and choose New team.

  1. Click Teams
Create a team · Click Teams
  1. Click New team
Create a team · Click New team
  1. In Name of the team, type Security team
  2. In What is the team for? (may be empty), type Reviews changes on security
Create a team · In Name of the team, type Security team; In What is the team for? (may be empty), type Reviews changes on security
  1. Click Create team
Create a team · Click Create team
Create a team · The team is there, without members yet.
Step 6 / 8

Members, a role and a duty

Add members with Add a member. Under Roles of the team switch a role on: every member gets its rights. Under Decides as switch a duty on: the members then decide as Security on changes and the governance profile. Every change is saved at once.

  1. In Add a member…, choose Tom Fisher
Members, a role and a duty · In Add a member…, choose Tom Fisher
  1. Click Auditor
Members, a role and a duty · Click Auditor
  1. Click Security
Members, a role and a duty · Click Security
Members, a role and a duty · Tom Fisher is a member; Auditor and Security are on.
Step 7 / 8

Rights: who may do what, and why

Rights shows per person and per part the level: None, View, Edit or Manage. Under each level it says where it comes from: as owner, as Team member or through team Security team. Someone gets the highest level of their role and all their teams. You do not change rights per box but through the role or the team, so it always shows why someone may do something.

  1. Click Rights
Rights: who may do what, and why · Click Rights
Rights: who may do what, and why · For Tom Fisher: View in every part, through team Security team or as Team member.
Step 8 / 8

Roles for decisions: who decides what

Roles for decisions sets per person the duties someone decides with at a gate: Management, Back office, Project manager, Scrum master, Architect, Tester and Security. A filled box was given here; an open box someone already holds another way, through a role or a team, or as owner. Click a box to give a duty, also to yourself; the message lets you undo it. Under the table each duty says in one sentence what it opens.

  1. Click Roles for decisions
Roles for decisions: who decides what · Click Roles for decisions
  1. Click Management for yourself
Roles for decisions: who decides what · Click Management for yourself
Roles for decisions: who decides what · A message: Management granted, with Undo.
Roles for decisions: who decides what · Back office: looks after the administration, and opens the rates and the cost rate per person.

This guide was carried out step by step on 27 Oct 2026 by an automated test on Flow (version 7d21bad8).