Your team
Invite the people who work on your sites with you. Everybody can edit everything; what the roles decide is who can change the team itself and who can spend money.
The short version
- Invite people from Organization settings, on the Team tab. Click your organization's name at the top of the screen to get there.
- Everybody can build and edit, whatever their role.
- Only owners and admins can change the team or the billing.
- There is one owner, and ownership can be handed over.
- Team members are not the same thing as site members.
The three roles
User can do all the work: build and edit sites, add pages, run the shop, send email, handle form entries and members, everything about the content. What they cannot do is change who is on the team or touch the billing.
Admin can do all of that, plus invite and remove people, and manage the subscription and payment details.
Owner is an admin who also owns the workspace. There is exactly one. Only the owner can change somebody's role or hand ownership to somebody else.
These are not seniority levels
It is worth being clear about this, because three names in a row look like a ladder and this is not one. The line is between the workspace and the work inside it, not between junior and senior.
A designer who rebuilds your whole site is a User. So is the person who runs your shop and answers every form submission. Neither needs to see your card details to do any of it, and making them an admin so they can get on with their job is a mistake the roles are shaped to make unnecessary.
Inviting somebody
Enter their email address and choose a role. They get an email with a link. If they do not have an account they can create one while accepting, so there is nothing for them to set up first.
Invitations go one address at a time, and the link in each one lasts seven days. If it runs out before they accept, invite them again.
Invitations nobody has accepted yet are listed under the team, with the role and the day the link runs out. Anyone on the team can see them; owners and admins can revoke one, which stops its link working at once and lets you invite that address again.
Changing somebody's role, or removing them
Both are on the Team tab, next to the person. Owners and admins can remove people; only the owner can change a role. Removing somebody takes away their access immediately; it does not touch anything they built, which belongs to the workspace rather than to them.
The owner cannot change their own role or remove themselves. Hand ownership over first if that is what you are trying to do.
Handing over ownership
The current owner can make anybody on the team the owner instead, with Make owner next to their name. It takes effect straight away, and the previous owner becomes an admin.
Undoing it needs the new owner's cooperation, since they are the only one who can hand it back. Worth being sure before you press it.
If your chamber of commerce uses Pilaster
When your website belongs to a chamber that runs on Pilaster, chamber staff can come over from Pilaster without signing in again, and they join your team the first time they do. The chamber's owner arrives as the owner if your team has none, and otherwise as an admin; its admins arrive as admins and its staff as Users. Board members and volunteers do not reach the website.
Their role follows Pilaster: when a chamber changes somebody's role there, or they leave, the change reaches your team too. The owner here is never changed or removed that way.
Team members and site members are different
Your team is the people who work on your sites here. Your members are visitors who log in to a site you published, which is a completely separate list with no access to this workspace at all.
Adding somebody to your team does not give them a login on your website, and adding a member to your website gives them nothing here.
When a control is showing but you cannot use it
Restricted things are shown locked with the reason next to them, rather than hidden. So if you can see it and cannot use it, the sentence beside it says which role you would need, and you know the feature exists rather than wondering.