Dashboard

Team & editors

Two different audiences: collaborators who use the dashboard, and content editors who log into the overlay on your live site.

Two lists — don’t mix them up

Team (Members) controls who can open app.macrocontent.dev for this website. Users (Content editors) controls who can sign in on the live site to edit with the overlay.

Collaborators (Team)

Open Team in the website sidebar. Invite people by email. They accept and then appear as members with a dashboard role:

Name	Type	Description
`Owner`	`role`	Project owner — full control including destructive actions and ownership transfer.
`Admin`	`role`	Full access to settings (keys, tokens, domains, team management).
`Editor`	`role`	Manage and edit content-oriented areas in the dashboard.
`Viewer`	`role`	Read-only dashboard access for this website.

Only the owner or an Admin can invite and change roles.
Admins can typically promote/demote Editors and Viewers; ownership transfer is a separate owner flow.
A linked-editor badge may appear when a collaborator is also connected as a content editor.

Site users / content editors (Users)

Open Users (Content editors & roles). These accounts sign in on your website — not in the dashboard — to open the overlay and edit content. After you create an editor, assign roles and permissions (including the baseline “everyone” role that applies to all editors).

Overlay login

Editors use the site’s editor login (shortcut / login UI from the SDK overlay). See the Editors handbook for day-to-day editing. Developers configure overlay login in quickstart.

Who does what

Invite a collaborator

Team → Invite team member → Admin, Editor, or Viewer.

Create a content editor

Users → add editor → assign roles for overlay permissions.

Give marketers and copywriters Users (overlay) access.
Give engineers and operators Team Admin/Editor for settings and tokens.
Use Viewer on Team when someone only needs to inspect the project in the app.

Don’t

Don’t expect a Team invite alone to unlock overlay login on the live site.
Don’t hand every collaborator Admin if they only need content access in the app.
Don’t confuse API token team_manager automation with inviting humans in the UI.

Can one person be both?

Yes. Someone can be a dashboard collaborator and a content editor. The Team list may show a linked-editor indicator when those identities are connected. Still manage each surface separately: dashboard roles vs overlay roles.

Automating team changes

Management API routes under /management/team/site-users use team.site_users:* permissions. Dashboard JWT collaborators are a separate platform concern. Prefer the UI for human invites; use API tokens with the team_manager preset for scripted editor provisioning. See Management API.