Team and workspaces
Workspaces as the billing root, inviting teammates, per-site access, the three roles and what each can do, and how to hand off ownership.
A workspace is the billing root: it owns a plan, a Stripe subscription, a set of sites, and a member roster. Most accounts have exactly one; you can create more to keep clients or projects on separate plans.
Workspaces
Each workspace has its own sites, members, and plan: usage and billing never mix across workspaces. Switch between workspaces you belong to, or create a new one, from Dashboard → Workspaces. Creating a workspace makes you its owner.
Inviting teammates
Owners and admins can invite by email from Settings → Team. mrkr emails the invite automatically; the invite link is also shown in the UI in case the email doesn't land. Invites expire after 7 days.
An invite is strictly bound to the email address it was sent to: accepting it requires signing in with a verified email that matches exactly. Forwarding an invite link to someone else does not grant them access.
Per-site access for members
Members (not owners or admins) can be scoped to either the whole workspace or a specific set of sites. An owner sets this from each member's Manage access control: pick "All sites" or check individual sites. A member with no grants at all sees nothing until an owner assigns them access.
Roles
| Role | Can do | Cannot do |
|---|---|---|
| Owner | Everything: billing, plan changes, invite/remove anyone, delete the workspace, change any role. | Nothing. |
| Admin | Invite and remove members, configure sites, see all data, manage billing. | Remove the owner, change the owner's role, delete the workspace. |
| Member | Read-only dashboards for the sites they've been granted (or every site, if scoped workspace-wide). | Invite, configure sites, touch billing, or write anything. |
Transferring ownership
There's no single "transfer" button. Do it in two steps: as the current owner, change another member's role to Owner (a workspace can have more than one), then optionally demote yourself to Admin or Member once they're confirmed as owner. The last-owner guard means you can always demote yourself as long as someone else already holds the Owner role.
Leaving a workspace
There's no self-serve "leave" action. Ask an owner or admin to remove you from Settings → Team, or (if you're the owner) transfer ownership first, then have the new owner remove you.