Inviting your team
Add teammates to a workspace, choose what each role can do, and transfer ownership, all without sharing a password.
Teammates join a workspace, and from there they can reach every project inside it. Nobody ever needs to share a login.
Inviting someone#
Open Workspace → Members and press Invite teammate. Enter an email address, pick a role and press Send invitation.
They get a link that adds them to the workspace. If they do not already have a LaunchList account, the same link walks them through creating one.
Pending invitations are listed on the same page, where you can choose Resend invitation or Revoke invitation from a row's menu.
Roles#
Rather than a fixed ladder, roles are sets of permissions, and What each role can do on the Members page shows you exactly what each one can do. That matrix is generated from the same permissions the server enforces, so it cannot drift from reality.
Broadly:
| Role | Can |
|---|---|
| Owner | Everything, including changing the plan, transferring the workspace and deleting it |
| Admin | Runs the team and the product, and can see the plan and invoices |
| Member | Builds and ships: pages, forms, campaigns, audience. No team or billing surface |
| Viewer | Read-only across projects, audience and analytics. Cannot edit and cannot export |
Three things stay with the owner alone, and none of them are configurable: changing the plan, transferring the workspace, and deleting it. An Admin can open the plan and the invoices, because someone running the team usually needs to know what it costs, but the person being charged is the only one who can change what is charged.
A Member is the default collaborator and deliberately stops short in three places: spending credits is money, taking a project live is a one-way company decision, and deleting a project quietly takes those contacts off your bill.
Seats#
Free is just you. Inviting a teammate starts on Collect, which includes 3 team members; Launch includes 10 and Grow is unlimited. For more seats, move up a plan. Your allowance and current usage are both shown on the Members page, read from the same plan definition the server enforces.
Pending invitations count as used seats. An invitation you sent and nobody accepted still occupies one, which is why revoking stale ones frees capacity.
If a workspace moves to a plan with fewer seats, nobody is removed: everyone already on the team keeps their access, and new invitations wait until there is room.
Removing someone#
On Workspace → Members, open their row's menu and choose Remove from team. Access ends immediately.
Anything they made stays: their pages, their campaigns, their imports. Work belongs to the workspace, not to the person who did it, so a leaver never takes content with them.
API keys they created also keep working, for the same reason. Keys belong to the workspace, so somebody leaving never breaks a running integration. Revoke a key deliberately if you want it gone.
Transferring ownership#
An owner can open another member's row menu on Workspace → Members and choose Make owner. Every workspace has exactly one, so this hands over rather than adding a second.
Do this before you leave a workspace you own, not after: an owner cannot remove themselves while they are the only one.
Leaving a workspace#
Anyone who is not the sole owner can leave from Workspace → General, under Danger zone, with Leave workspace. Your personal workspace stays yours; leaving a shared one does not touch it.
Next#
- Plans and billing
- API authentication: why keys survive people leaving
Common questions
How do I add someone to my LaunchList account?
Open Workspace → Members, invite them by email address, and pick a role. They get a link that adds them to the workspace. Nobody ever needs to share a password.
Can I stop a teammate from seeing billing?
Members and Viewers have no billing surface at all. An Admin can see the plan and the invoices but cannot change them: changing the plan is owner-only, and that is not configurable.
Do pending invitations use up a seat?
Yes. An unaccepted invitation counts toward your seat total, so a workspace cannot get extra capacity by leaving invitations outstanding.