Collaborators & roles
| Role | Can do |
|---|---|
| Owner | Everything, including hosting, sending setup, payments, and deleting or transferring the site. |
| Designer | Everything in the editor: content, layout, Site Styles, exact values, locks, publishing and rollback. |
| Editor | Content only — text, images, pages, posts, the inbox — and publishing. Can’t change layout or styles. |
| Contributor | Writes blog posts and events as drafts for approval. Can’t publish. |
Roles are enforced by the Hub, so they apply to everything — Studio, the inbox, and any AI connected with that person’s account. (Contributors can’t connect an AI.)
Invite someone
Section titled “Invite someone”Settings → People → Invite: enter an email address or a GitHub username (@name) and choose a role. They get an invitation link; people without a GitHub account get the same guided sign-up as owners. Pending invitations can be cancelled, and roles changed or removed any time.
Lock sections
Section titled “Lock sections”A designer can lock sections so editors change only the words and images, not the layout — perfect when handing a site to a client. Locks are set per person, page by page, under People → Section locks.
Approvals
Section titled “Approvals”Contributors’ posts and events wait in Approvals. Approve to publish them with the next publish, or send them back with a note.
Working together
Section titled “Working together”Everyone edits the same live draft: you see who’s editing, and changes from others appear as they happen. If two people change the very same thing at once, the most recent change wins and the other person sees a notice with a way to restore their version.
Handing a site over
Section titled “Handing a site over”Building for someone else? From the dashboard, Transfer ownership moves the site — files and all — to the client’s own GitHub account after they accept. You can stay on as a designer.
A note for technical collaborators
Section titled “A note for technical collaborators”Collaborators are added to the site’s GitHub repository with write access, because that’s where the files live. Someone comfortable with Git could change files directly and bypass roles; give the Owner and Designer roles to people you trust with the site.