Create a team and invite members to manage a site together

Last updated: 2026-10-12

At a glance

Time needed

About 5 min

Plan required

Team Plus

Coding knowledge

None

Where to do it

Account

Step by step

1. 1

   Create a team — Team Plus and up

   The Team page (/team) is visible on every plan, but actually creating a team and using member seats is a Team Plus-and-up feature. On Free, Plus, Pro, or Max, the page shows an upgrade prompt instead, and the Create team button only becomes active once you're on Team Plus or higher. Say Momo Coffee's owner upgrades to Team Plus and creates a team called Momo Coffee.

   

2. 2

   Invite members and set their roles

   Once a team exists, invite people by email from the Members tab. Roles run Owner > Admin > Editor > Viewer — the Owner is fixed to whoever created the team, and Owner/Admin can change everyone else's role. Admins manage invites, removals, and resource allocation; Editors can edit and publish team sites; Viewers can only look. Momo Coffee's owner invites two staff members as Editors to share site management.

   Team › Members

   Me (Momo Coffee) Owner

   Staff 1 Invited as Editor

   Staff 2 Invited as Editor

   Seats used 3 / 5
3. 3

   Resources are carved out of your plan — not added on top

   This is the part people get wrong most often. The sites, storage, and domains you allocate to a team aren't extra resources from somewhere else — they're a share of your own (the owner's) plan total. So your personal share is always “plan total minus what you've given the team.” To make this concrete: say your plan's site limit is 80 total. The moment you allocate 10 to the Momo Coffee team, your personal share drops to 70. Storage and domains work the exact same way.

   Team › Resources (example numbers)

   Sites (80 total) Team 10 · Personal 70

   Storage (60GB total) Team 5GB · Personal 55GB

   Custom domains (30 total) Team 2 · Personal 28
4. 4

   Seats — how many members you can invite — are capped separately

   Sites, storage, and domains are a pie you slice, as you just saw. Seats — how many members a team can hold — aren't part of that pie at all; they're a separate cap. The default is 5 and it varies by plan, and it's checked purely on member count, regardless of how much of the pie you've allocated. If Momo Coffee's team has 2 staff plus the owner, that's 3 of 5 seats used, independent of the resource split above.

   Team › Resources › Seats

   Seats used 3 / 5

   Seat limit 5 by default (varies by plan)

   Relation to resource allocation Separate — not part of the sites/storage/domains pie

Frequently asked questions

Read next

• Audit log — see who changed what, and when How to check your account's audit log in Account settings › Developer and export it as CSV — personal logs are free on every plan, team logs need Team Plus or higher (English)
• Transfer ownership — hand a site to another person or team How to transfer site ownership to another person or team — verification codes, consent, and the 24-hour cooling-off window (English)
• Managing your sites — folders, rename, delete & recovery How to organize sites into folders, rename them, and undo a deletion within 7 days from the /sites dashboard (English)
• Check your billing history and request a refund How to check payment history on /billing and request a refund on Yave Pay within 24 hours of an unused payment (English)