Team Collaboration
Work together with your team by inviting members into the workspace and giving the right people access to each project.
Inviting Team Members
How to Invite
- Go to Members
- Click Invite Members
- Enter their email address
- Select their workspace role
- Send the invite
The invitee receives an email with a link to join your workspace.
Team member limits depend on your plan. See pricing for details.
Roles & Permissions
The Members page currently supports these assignable workspace roles:
| Role | What it covers |
|---|---|
| Workspace Admin | Full workspace access, including members, projects, billing, and settings. |
| Team Lead | Can add projects and manage day-to-day feedback on the projects they are assigned to: comments, replies, statuses, tags, widget settings, and CSV export. |
Team leads cannot:
- Delete a project, or change its name or domain
- Manage billing or the subscription
- Invite or remove members
- Change account-level settings
These actions are reserved for workspace admins. When a team lead opens a project's General settings, the configure and delete controls are replaced by a notice pointing to a workspace admin.
Workspace owners appear separately in the members list and retain full workspace access.
Managing Members
Use the Members page to review who is in your workspace, see how many seats are in use, and keep member access up to date as your team changes.
For larger teams, your backend can create members through the REST API. An automation can send one request per employee, so you do not need to enter everyone manually. API-created members still need the owner's approval under Workspace settings → Company login before using SSO. See Company login for account matching, first login, and the current restriction on API access when SSO is required.
Project-Level Access
Control access at the project level from the project's Access Settings:
- Open the project you want to manage
- Go to Access
- Use the Team Members section to assign or remove project access
This is useful when:
- Different teams manage different websites
- Clients should only see their own project
- Contractors need a limited project scope
Collaboration Tips
For Agencies
- Create separate projects per client
- Use project-level access to keep client work isolated
- Configure notifications per project so the right team gets alerted
For Product Teams
- Use statuses to reflect your review workflow
- Connect Slack or webhooks for faster follow-up
- Restrict project access when outside collaborators are involved
For Support Teams
- Use priorities and statuses to triage incoming feedback
- Keep replies inside comment threads so context stays together
- Review project access regularly as responsibilities change