Team workspaces: one shared set of projects, three roles
On the Team plan, your workspace (projects, live sites, domains and the data visitors send) is shared with the people you invite. Each person is an owner, an admin or a member. Members build, edit and publish; admins also manage people, delete projects and take sites down; only the owner changes roles and pays. Everything stays on the owner's account, so removing someone ends their access at once.
Why roles matter on a shared site
When several people work on the same websites, most mistakes aren't malicious; they're someone with too much reach. A designer tidying old projects deletes the one a client still needs, or a junior takes a live site down while testing. Sharing one login avoids none of that and loses the record of who did what. Clear website builder team roles fix it by giving the people who make the work the tools to make it, and keeping the destructive actions with fewer hands.
What each role can do
| Action | Member | Admin | Owner |
|---|---|---|---|
| Build, edit and publish projects | Yes | Yes | Yes |
| Invite people and cancel invitations | No | Yes | Yes |
| Remove a member | No | Yes | Yes |
| Remove an admin | No | No | Yes |
| Delete projects and take sites down | No | Yes | Yes |
| Change someone's role | No | No | Yes |
| Billing | No | No | Yes |
The owner is the person who holds the Team subscription. Anyone can leave a workspace they've joined, whatever their role. Each request is checked against the person's role on the server at the moment they make it, so a change of role or a removal applies straight away rather than at their next sign-in.
Inviting people
The Team page in the dashboard shows who's in the workspace and how many seats are used. To add someone, the owner or an admin enters their email and picks a role; the form describes Member as builds, edits and publishes, and Admin as also inviting people and taking sites down.
- Anticode emails a link to that address. It works once, only for that address, and for seven days.
- The person signs in or creates an account with that email and confirms it. A link opened from a different account is refused.
- They join with the role they were invited with, and the workspace's projects appear in their Projects list.
- Inviting the same address again replaces the earlier invitation and its link.
Pending invitations count as seats until they're accepted, cancelled or expire. A Team workspace has ten seats by default, the owner included; when every seat is in use, the form says so and asks you to remove someone or cancel an invitation first. You can also rename the workspace, so members see a name they recognise rather than the owner's.
What's shared, and what isn't
- Shared: the workspace's projects and published sites, its domains, form submissions, and its connectors and payment link, which belong to the workspace rather than to one site. Members also build at the Team plan's limits.
- Not shared: anyone's own personal projects outside the workspace, and billing.
- Not transferable: projects can't be moved between separate accounts, so work meant for the team should be started inside the workspace.
Because the data stays on the owner's account, nothing has to be handed back when someone leaves. Their access ends, and the projects they worked on stay where they were. The set up a team website workspace workflow walks through a first setup, and removing an employee's access covers the other end.
Two-factor sign-in and publishing
A site that collects visitors' data, through a form or a booking, can't be published until two-factor sign-in is turned on for the account that holds that data and for whoever publishes it. In a workspace that means the owner, and the teammate pressing publish if it isn't the owner. The publish check names whose account is missing it.
Limits
- Three roles, not custom permissions. There's no per-project access: a member can work on every project in the workspace.
- If the subscription lapses, sharing stops. Members lose access to the workspace until it's renewed.
- One workspace per Team subscription. Agencies who need white-label client sites use the Agency plan, which is a Team workspace with its own allowance and seat count; see white-label for agencies.
- Prices and seat counts by plan are on /pricing.
Questions people ask
Can a member delete a project or take a site down?
No. Members build, edit and publish. Deleting projects and taking sites down is for admins and the owner.
Can an admin make someone else an admin?
No. Only the owner changes roles. An admin can invite someone as an admin, and can remove members but not other admins.
Do pending invitations use seats?
Yes, until they're accepted, cancelled or expire after seven days.
What happens to a project when its builder leaves the team?
Nothing. Projects belong to the workspace owner's account, so they stay in the workspace.