Flow Guide All guides ↗
Every section

Your organization

The people in your workspace and how they're grouped: members, teams, pods, roles, custom fields, billing and more than one organisation. Each section says what it's for, who sees and changes it, and how to do the main jobs there.

🧑‍🤝‍🧑

Members

Everyone in your workspace, the access each person has, and the invitations still waiting.

Owner · Admin manage people
Organization › Members

The Members tab lists each Person with their Access (Owner, Admin, Member or Stakeholder), their Seat (Paid or Free) and when they Joined. Owners and Admins also see a Two-factor column. Find someone with Search by name or email and the role filter (All roles).

Inviting, changing access and removing people are for Owners and Admins only, and only they see Invite member and the Pending invites tab. Members and Stakeholders see the list of people and nothing to change.

Invite someone

  1. Click Invite member and enter their Email.
  2. Choose their Access. Only levels below your own are offered: the Owner can invite Admins, Members and Stakeholders; an Admin invites Members and Stakeholders.
  3. Optional: under Add to a project (optional), pick a project and choose As — Scrum Master, Developer or Stakeholder. A Stakeholder invite always joins a project as a Stakeholder. The Product Owner is chosen on the project itself.
  4. Click Send invite. They get an email. An Invite link with Copy link also appears, if you'd rather send it yourself. Invite links last 48 hours.
🪑Seats — the Owner, Admins and Members each take a Paid seat. Stakeholders take a Free one, up to two for every paid seat. On a paid plan, the seats you've bought are the most members you can have — and a pending invite to a paid level holds a seat too, until it's accepted or revoked. When they're all in use, the invite form says so and links to Billing.

Look after pending invites

  1. Open the Pending invites tab. Each invite shows when it expires.
  2. Invite still valid but lost? Use the row's ⋯ › New invite link…. Flow asks first, because the new link replaces the one in their email and the old link stops working.
  3. Invite expired? Click Resend on its row.
  4. Changed your mind? Use ⋯ › Revoke invite…. The link stops working, and you can invite them again later.

You can only act on invites to a level below your own, so an Admin can't change an invite to another Admin.

Change someone's access

  1. On the Members tab, pick a new level from the Access dropdown on their row.
  2. Changing someone to Stakeholder asks first. They become a Stakeholder on every project too, so they stop being a Product Owner or Scrum Master anywhere. Click Make Stakeholder to confirm.

You can only change people below your own level, and only to a level below yours. So only the Owner makes Admins, and an Admin can't change another Admin. Your own row can't be changed here.

Remove someone, or reset their two-factor

  1. Open the ⋯ menu on their row.
  2. Remove from organization… takes them out straight away. They lose access to its projects and leave its teams and pods. Their work items and comments stay, and their seat is freed. You can invite them again later.
  3. Reset two-factor… is only for the Owner, and only for someone who has two-factor on. Use it when they've lost both their phone and their recovery codes. They're signed out everywhere and can sign in with their password until they set up two-factor again.
🤝

Teams

Your delivery teams: the people who ship work together, each team with a Team manager.

Owner · Admin · Team manager
Organization › Teams

A team is a group of people who deliver together. A project set to Team visibility opens to everyone on that team, so a team is also a simple way to decide who can open a project. Click a team to open it in a side panel.

Owners and Admins see and manage every team. A Member whose custom role gives See every team and pod (for the whole organisation) sees every team too, without changing them. Everyone else sees only the teams they're on. A team's Team manager can edit that team and change its people. What anyone may do inside a project still comes from their role in that project.

Create a team

  1. Click New team, give it a name and, if you like, a Description, then click Create team. You become its Team manager.
  2. Open the team and click Add people. Choose a person and their Team role — Team manager or Member.
  3. Or click Add from a pod, choose a pod and click Add everyone. This copies the pod's people into the team once. Later pod changes don't reshuffle the team.
🔑Who can create teams — Owners and Admins, and a Member who has a custom role with Create teams given for the whole organisation (see Roles & custom roles). Free includes 1 team, Starter 3, Business as many as you need.

Change, leave or delete a team

  1. To rename it, use the row's ⋯ › Edit team… (Owners, Admins and its Team manager).
  2. To take someone off, click Remove next to their name. Nobody can change or remove someone with a higher organisation role than their own.
  3. Anyone can take themselves off a team with Leave team on their own row. If the team opens projects for them, Flow says so first.
  4. To delete it, use ⋯ › Delete team… (Owners and Admins only). Projects that used the team for access become Private, with the team's current people kept on them, so nobody loses access.
🧱

Pods

Your capability areas, such as Frontend, QA or Design: long-lived groups of people, teams and projects.

Owner · AdminStarter plan & up
Organization › Pods

A pod groups people by what they're good at, rather than what they're shipping right now. Teams come and go, pods stay. You can link a pod's projects and teams, and its panel shows how work is flowing across them.

Creating and changing pods is for Owners and Admins. They see every pod, as does a Member whose custom role gives See every team and pod; everyone else sees only the pods they're in. Starter includes 1 pod, Business as many as you like, and the Free plan has none.

Create a pod

  1. Click New pod. Give it a name, a Description and an Ownership type (Individual, Committee or Open), then click Create pod. You become its owner.
  2. Open the pod and click Add people. Choose a person and their Pod role — Owner, Contributor or Member.
  3. Click Link project to count a project's work in the pod's numbers, and Link team to group a team under the pod.

Read the pod's flow

  1. Open the pod. The Flow, last 30 days tile shows how many items were Finished, the Average cycle time and the Points completed, from the linked projects' daily numbers.
  2. A new pod shows dashes until its first day is counted.
💡A pod never opens a project — linking a project or a team, or adding someone to a pod, doesn't change who can open anything. Access comes from a project's visibility and its People list. To put a whole pod on a team, use Add from a pod on the team.

To rename a pod, change its owner or delete it, use the row's ⋯ menu (Edit pod…, Delete pod…).

🔑

Roles & custom roles

The built-in roles everyone has, and custom roles that add a few abilities for chosen people.

Owner · Admin
Organization › Teams › Custom roles

Everyone has two built-in roles. Their access to the organisation (Owner, Admin, Member or Stakeholder) is set on Members. Their role in each project (Product Owner, Scrum Master, Developer or Stakeholder) is set in that project's Project settings › People. Most companies need nothing more.

A custom role only ever adds abilities to the people you give it to. It never takes any away. Custom roles are for Owners and Admins: only they see the Custom roles tab, create, edit and give roles. Deleting a role is the Owner's.

Make a custom role

  1. Open Teams, choose the Custom roles tab and click New role.
  2. Give it a name and a Description, and tick its Permissions (listed below).
  3. Click Create role.

Give it to someone

  1. Open the role and click Give to someone.
  2. Choose the person, then under Where choose The whole organisation or one project. On one project, the role counts only in that project.
  3. Click Give role. To take it back, click Remove next to the person under Given to.

What a custom role can add

GroupPermissionGood to know
Work itemsCreate work items · Edit work items · Delete work items · Choose who a work item is assigned toDelete lets them delete any work item.
SprintsCreate sprints · Start sprints · Complete sprints—
ProjectsChange project settings · Add and remove project membersOpens the matching tabs of Project settings for them. Add and remove project members never makes anyone a Product Owner or Scrum Master, or changes those roles.
OrganisationCreate projects · Create teams · Create and change company, team and pod goals · See every team and podWhole organisation only: these count only when the role is given for the whole organisation, and never for a Stakeholder. The goals permission covers company and team goals (optionally tied to a pod) — any goal not tied to one project. Seeing every team and pod doesn't let anyone change them. Project goals stay with each project's Product Owner.
CommentsPost comments · Delete commentsPost comments is marked Not needed (everyone who can open a project may comment). Delete comments is marked Not enforced yet (comments can't be deleted).
🧑‍🏫The built-in Agile coach role — some organisations also have a built-in role called Agile coach (marked Built-in). It holds the four Organisation permissions: create projects and teams, create and change company, team and pod goals, and see every team and pod. It's always given for the whole organisation. It can't be edited or deleted, but Owners and Admins can give it and take it away like any role. If your organisation doesn't have it, make a role with those four permissions.
🏷️

Custom fields

Extra fields every work item can carry, in every project, for things the built-in fields don't cover.

Owner · Admin
Organization › Settings › Custom fields

Custom fields belong to the whole organisation: a field you add appears on work items in every project. You can have up to 50. Owners and Admins add, change, order and delete them. Nobody else opens organisation settings — everyone else meets custom fields on the work items themselves.

Filling in a value happens on the work item itself, under All fields. Whoever may edit work items in that project can set it: its Product Owner, Scrum Masters and Developers, Owners and Admins, and anyone with a custom role that gives Edit work items.

Add a field

  1. Click New field and give it a name.
  2. Choose its Type: Text (up to 1,000 characters), Number, Date, Single choice, Multi choice (up to 50 options per item), Person (someone who can open the item's project), Link or Checkbox.
  3. For a choice field, add its options one per row (Add option adds a row).
  4. Click Add field. Drag the fields to set the order work items show them in.

Change or remove options

  1. Use the field's ⋯ menu › Edit. Renaming an option updates every work item at once.
  2. Removing an option that work items use asks What happens to those work items: Clear it from them, or Replace with another option. Each changed item gets one History row.
  3. Click Save changes.
⚠️Deleting a field deletes its values on every work item, and it can't be undone (past History rows stay). A field's type can change freely while no item has a value; after that only some changes are allowed, and the dialog tells you which.
🚦Make it required at a stage — a workflow stage's entry rules can require a custom field before an item moves in. See Workflows.
💳

Billing

Your plan, seats, invoices and billing details.

Owner · Admin see it · Owner changes the plan
Organization › Billing

The Billing page is only in the menu for Owners and Admins. Admins can read it, and can edit Billing details. Changing the plan, seats, card or subscription is the Owner's alone. Anyone else who opens the address sees "Only owners and admins can see billing".

New workspaces start on a free 14-day Business trial. In its last week, a banner at the top of the app says how many days are left. When it ends, the workspace moves to the Free plan and everyone keeps their access. See what each plan includes in Part 1 · Your plan.

Change your plan

  1. Choose Monthly or Annual under Billing period.
  2. On a plan card, click Choose with the plan's name. Enterprise says Contact sales.
  3. Paying in rupees with no state on file yet? Flow first asks Where is your organisation billed? — Indian GST depends on your state. Then you go to the secure checkout.
  4. Already paying? Flow shows the price of the change before you confirm it.

Change seats

  1. On the Seats tile, click Change seats.
  2. Enter the number of Paid seats and click Update seats. Stakeholders don't take a paid seat.

If you're billed by invoice rather than by card, the tile says Contact support to change seats.

Card, invoices and billing details

  1. Manage billing opens the payment portal, where the Owner updates the card and sees card invoices. If a payment fails, the page says so and points there.
  2. Invoices lists your invoices. Open one to view it.
  3. Under Billing details, click Add billing details (or Edit). Fill in the Legal name, GSTIN (optional), the state and the Billing address, then click Save billing details. Owners and Admins can do this.
🧾Paying in rupees? Your invoices need a state, because Indian GST depends on it. If you give a GSTIN, the state is set from it.

Move to the Free plan

  1. On a paid plan, click Cancel subscription. Flow says what changes before you confirm: when the plan ends, anything over the Free plan's limits, and features that won't open on Free.
  2. After a cancelled plan ends, Choose Free moves you to the Free plan.
💡Moving to Free removes nobody — nothing is deleted and everyone keeps their access. If you're over a Free limit, you just can't add more until you're back under it, and the data in paid-only features is kept for when you upgrade again.
🏢

More than one organisation

Belong to several organisations with one sign-in, and switch between them.

Anyone in two or more organisations
Organisation name (top of the sidebar)

One account can belong to several organisations — for example your company and a client's. Each organisation has its own projects, people, plan and settings, and you can have a different access level in each.

Join another organisation

  1. Open the invite email from that organisation and follow its link.
  2. The page says Sign in to join with the organisation's name. Sign in with your existing account (the invited email address) and you join straight away.

Switch organisation

  1. Click your organisation's name at the top of the sidebar. Under it you see your current plan.
  2. The Organisations list shows each one with your access there, and a tick on the current one. Click another to switch.
🔔Good to know — notification choices are kept per organisation, and an organisation that requires two-factor asks you to set it up before you use it.