The dashboard is organised in two levels. The workspace is your company or studio: the people who work with you, and every site you review. A project is one of those sites: its comments, the people who can see them, and the secret its preview builds use.
The workspace
The workspace’s name sits at the top of the sidebar. Its menu lists the workspaces you belong to, switches between them, and has Create workspace. Creating one asks for a name, then lets you invite your team or skip.
Members, in the sidebar, lists the people in the workspace and their workspace role. Invite someone by email: they join when they sign in to the dashboard with that address.
| Workspace role | What it gives |
|---|---|
| Owner | The workspace’s owner. Manages members and sees every project. |
| Admin | Sees and manages every project, and gets the review digests. |
| Member | Sees the projects they are added to. |
Members is about your team. Reviewers you invite to a single project are not listed there.
Projects
Each site you collect comments on is a project, created from Projects → New project. A project has its own:
- Comments, from the widget on your dev server, from review links, and from previews. See Comments.
- People, with a role each, and its review links. See People & roles.
- Allowed sites: the exact addresses the widget may run on. Comments from anywhere else are refused.
- Build secret: the
FEEDBACK_SECRETits preview builds use. A preview build needs nothing else to send its comments to the right project. See Project settings.
None of this is shared between projects: a reviewer on one project sees nothing of another.
A project’s people and roles
Everyone on a project’s People tab sees every comment on that project. Each has one of three roles:
| Project role | What it gives |
|---|---|
| Reviewer | Reads every comment, writes their own, replies to anyone. |
| Admin | Manages the project and its people, and gets review digests. |
| Owner | Also invites and removes people, resolves anyone’s comments and deletes the project. |
A project always keeps at least one owner. People invited by email sign in with GitHub, Google, Microsoft or an emailed code; there is no password. Reviewers on a review link need no account at all: their comments appear under the name you gave the link.
A workspace member added to a project takes the role the project gives them, so Ben can be a member of the workspace and an admin of one project.
Branches
Every comment carries a branch label. A comment written on your dev server is labelled with the Git branch checked out at the time, or default without Git or on a detached checkout. A comment on a preview is labelled with the branch the preview was built from.
Branches are labels, not something you create or manage. The Comments tab shows the label on each comment and filters by it, so the comments on one preview stay apart from another’s. A branch label never changes which file and line a comment points at.