Users, teams & roles
Each person in a project has a project role that sets what they can do. On paid plans you can also group people into teams, which decide which links and domains they work with.
Invite users
Open Users under Workspace, enter an email and pick a role. People without an account get an email to set their password. The number of users depends on the plan (1 on Free, 2 on Starter, 5 on Pro, 20 on Business). A project always keeps at least one Owner.
Project roles
| Role | Can | Typical person |
|---|---|---|
| Owner | Everything, including billing, API keys, webhooks and deleting the project. | The account holder |
| Admin | Everything except API keys and webhooks: all links, domains, users, teams, settings and billing. | Head of marketing, agency lead |
| Developer | API keys and webhooks; view, create, edit and delete every link; view domains and analytics. Doesn't add domains or run teams. | The engineer wiring up your stack |
| Member | View, create and edit links (not delete); view domains and analytics. Works inside their teams: their own links plus their teams', and new links only on their teams' domains. | Media buyer, content creator |
| Analyst | Read-only: links, domains and analytics. | Reporting, client viewer |
| Billing | Plans, invoices and payments only. | Finance |
Teams
Starter+ 1 team on Starter, 3 on Pro, unlimited from Business. Owners and Admins create teams on the Teams page, then add users and choose which domains the team may publish on.
| Team role | Adds on top of the project role |
|---|---|
| Leader | Full control of the team's links (including delete); sees all of them. Can add and verify domains for the team, rename it, switch it between private and public, and manage its members. Can make API keys and webhooks. |
| Member | Views, creates and edits links in the team. Can make API keys and webhooks limited to what they can do. |
Team roles only ever add permissions. Only Owners and Admins can appoint a Leader or delete a team.
Private and public teams
| A team member sees | A team member can edit | |
|---|---|---|
| Private | Only the links they made | Their own links |
| Public | Their own and their teammates' links | Their own links |
The Leader always sees and manages all of the team's links. Owners, Admins and Developers see every link in the project.
Example: an agency with two client teams
Your agency runs campaigns for two clients in one project, each with its own domain, and buyers shouldn't see each other's work.
- Add go.client-a.com and go.client-b.com under Domains.
- Create teams Client A and Client B, both Private.
- Give Client A the domain go.client-a.com, and Client B go.client-b.com.
- Invite the buyers with the project role Member, and add each to their client's team.
- Make each account manager Leader of their client's team.
- Invite the client as an Analyst if they want to see the numbers.
Buyers now only publish on their client's domain and only see their own links; account managers see and manage the whole team. If the clients' work should be in fully separate billing, use a project per client instead.