Team & resources

To add someone to the project's team, choose Team in the project sidebar, then Invite member. Type their Email Address, pick a role under Set Role, and choose Send Invite. Only the email is required: Send Invite stays disabled until there is one.

• Set Role: Admin, Member or Viewer. New invites are Member.

The person joins the team list straight away as Active, named after the part of their email before the @. Flow doesn't send them an email. Each email can be on a project's team once, so inviting an address that's already there fails with Couldn't invite member.

The team list and its roles are a record of who works on the project. Adding someone here doesn't let them open the project, and their role doesn't change what they can do in Flow. Everyone in your organization can open its projects, so add new people to the organization in Dash.

The figures across the top of Team count the project's team: Total members (with how many are active), Admins, Members and Viewers. Search and filters don't change them.

Each row shows the member's name and email, their role and their status. Members are listed in the order they joined, oldest first. Narrow the list by role with the filter (All Roles, Admin, Member or Viewer), or type in Search members to match names and emails.

The list shows 10 members a page unless the project's default is changed under Settings → General → Default rows per page. Choose 10, 25, 50 or 100 at the bottom to change it for the list you're looking at.

Each row's ⋯ menu on the Team screen has Edit Role and Remove.

• Edit Role opens Edit Member Role. The email can't be changed there: pick the new role under Set Role and choose Save Changes.
• Remove asks you to confirm first. Once you choose Remove in the dialog, the member leaves the team list. Flow can't restore them, but you can invite the same email again.

To change a member's email, remove them and invite the new address.

Resource Allocation plans who works on the project and how much of their time it takes. It has two tabs.

• An allocation assigns a person to project work at a load from 0% to 100%, with optional start and end dates. Its status is Active, Planned or Completed.
• A resource request asks for extra capacity, such as another designer. It stays Pending until someone approves or denies it.

The two aren't linked: approving a request doesn't create an allocation, and an allocation's status doesn't change on its own when its end date passes. The person on an allocation is a name you type, not someone picked from the team list.

Choose Resource Allocation in the project sidebar, then New Allocation. Only the member is required: Create Allocation stays disabled until there is one.

• Member: the person's full name.
• Role: what they do on the project, like Backend Engineer.
• Status: Active, Planned or Completed. New allocations are Active.
• Allocation: their load, as a whole percentage from 0 to 100. It starts at 50.
• Starts on and Ends on: optional dates.
• Notes: anything worth remembering about the allocation.

The Allocations tab lists every allocation, newest first, with its member and role, status, load, start and end dates, and notes. A warning icon beside a name marks an overloaded allocation: one over 80% that isn't Completed.

The figures across the top of Resource Allocation are Total load (every allocation's percentage added up, with how many are over 80%), Active, Planned and Pending requests. Search and filters don't change them.

Filter by status (All Statuses, Active, Planned or Completed), or search by member, role or notes. When nothing matches, Clear filters resets both.

Each row's ⋯ menu has Edit, which opens the same form, and Delete. Flow asks you to confirm a delete, and a deleted allocation can't be restored from Flow.

To ask for extra capacity, open the Requests tab in Resource Allocation and choose New Request. Requester (who is asking) and Request (what they need) are required: Create Request stays disabled until both are filled in. Target names what's needed, like Designer or QA tooling, and Requested on is today's date unless you pick another.

New requests start as Pending. Each row's ⋯ menu has Approve and Deny while a request is Pending, and Reopen, which sets it back to Pending, once it's decided. Delete asks you to confirm first, and a deleted request can't be restored from Flow.

Requests are listed newest first. Filter them by status (All Statuses, Pending, Approved or Denied), or search by request, requester or target.