Give a project a shared home
A workspace keeps the reviews, personas, reports, members, and integration settings for a body of work together. Your team can work from the same evidence instead of passing around disconnected screenshots and summaries.
For example, keep your storefront’s checkout reviews and GitHub repositories in one workspace. A separate product or client can have its own workspace, with different people, personas, and repository settings. Choose the workspace where the work belongs before starting a review or connecting an integration.
Workspaces, projects, and billing accounts
In the account-based setup, a billing account manages the subscription and shared project allowance. A project is backed by a shared workspace: it is the space where that project’s reviews and collaboration happen, rather than another folder inside a workspace.
A billing account can support separate projects, such as Storefront and Admin app. Account membership and a paid seat do not automatically grant access to every project’s content. Project membership determines who can open that workspace and its reviews.
You may also see personal or private workspaces in the switcher. Only you identifies a personal workspace; Shared identifies a shared one; Private to you identifies a private workspace. Use the visibility shown in the dashboard when deciding where to put work.
Create and switch workspaces
Open the workspace switcher to choose a workspace you can access. Switching changes the dashboard’s active context for reviews, personas, members, and integrations. It keeps existing review history in its original workspace.
For account projects, open Settings → Billing accounts, choose the account, and open its projects. When project creation is available, enter a Project name and choose Create project. Open the project to make it your active workspace.
The switcher’s Create workspace action leads to Billing accounts. Creation depends on the account’s product access, allowance, and your permissions; the dashboard shows whether you can proceed. Existing accounts may also offer a separate legacy workspace flow.
Invite the people who need the evidence
In the intended workspace, open Settings → Members. If your role allows membership management, choose Invite a teammate, enter their email, choose a Role, and select Send.
Choose access around the work someone needs to do:
- Owner or Admin: manage the workspace’s members and integrations, subject to the applicable permissions.
- Member: create and inspect reviews. A member can cancel their own runs.
- Viewer: read reviews, personas, and available artifacts without launching reviews.
A designer who needs to inspect findings may only need Viewer access. A teammate who will run reviews needs Member access. Give integration-management access to the people responsible for repository setup.
Invitations and available seats depend on your workspace or account terms. Check the allowance and any reason shown next to the invitation controls. The pricing page explains the published offers; your account’s displayed terms govern its available capacity.
Find and join a team workspace
Sign in with the email that received the invitation and accept the workspace invitation. Flock can show pending invitations for your verified email, alongside the workspaces you already have access to.
If a workspace you expect is missing, confirm your sign-in email and ask its owner or admin to invite you. Current membership is invitation-based; seeing another team’s name or sharing its company email domain does not grant access.
For an account-based project, you may need to accept an account seat invitation and a separate project invitation. The seat provides account product access; the project invitation provides access to that project’s workspace. Accepting one does not replace the other.
Where we’re taking Team
Our intent for Team is to make shared work easier to find and join: discoverable workspaces and a way to request access to the right one. Teammates should be able to find the work relevant to them, while the people managing the workspace keep control of membership.
Discovery and requests to join are planned capabilities, not available today. Use invitations for current access, and see pricing for the published Team direction.
Connect the repositories for this work
Select the intended workspace, then open Settings → Integrations → GitHub. An owner or admin can choose Connect GitHub and grant the Flock App access to the relevant repositories. A workspace can connect multiple GitHub organizations or personal accounts.
For example, connect your storefront and checkout repositories to the workspace where that team reviews the customer journey. Select the targets and personas for each repository, then enable its reviews. Installing the App makes repositories available; review activation is a separate step.
A GitHub App installation currently belongs to one Flock workspace. GitHub organization membership and Flock workspace membership are also separate: access in one system does not create membership in the other. Follow the GitHub App guide for installation, preview setup, and review activation.
Give your team a repeatable review workflow
Keep the personas and goals for a recurring journey consistent, and save the sign-in profile needed for authenticated reviews in the same workspace. Your team can then inspect comparable results after a change rather than reconstructing the setup each time.
Use the dashboard to read the review, GitHub to keep feedback beside a pull request, and MCP to work through evidence and repairs with a coding agent. MCP access has its own workspace consent; changing the dashboard’s selected workspace does not change an existing coding-agent connection.
Start with one useful shared review. Invite the teammates who need to inspect it, agree on the task and personas, and use the findings and evidence to choose the next change.