Teams and roles
Every account has a personal workspace. Create team workspaces to share projects, domains and billing.
| Action | Viewer | Developer | Admin | Owner |
|---|---|---|---|---|
| See projects, deployments, logs | ✓ | ✓ | ✓ | ✓ |
| Deploy, roll back, manage domains and variables | ✓ | ✓ | ✓ | |
| Create API tokens | ✓ | ✓ | ✓ | |
| Delete projects, manage members and webhooks, see billing | ✓ | ✓ | ||
| Change the plan, transfer or delete the workspace | ✓ |
Invites#
Admins invite by email. Invites expire after 7 days and can be resent or revoked; pending invites count as seats.
Transfer ownership#
The owner can make another Admin the owner from Settings › Members. They become an Admin.
Transfer a project#
Finished a site for a client? Hand it over from Project › Settings › Transfer project. Admins and the Owner can transfer.
- Move to one of your workspaces: pick the workspace and confirm by typing the project's name. It moves immediately.
- Send to someone else: create a transfer link, optionally emailed to your client. They sign in (or create a free account), pick one of their workspaces and accept. Links work once, for 7 days, and you can cancel them.
The site stays online throughout. Domains, deployments (with instant rollback), environment variables, databases and storage, cron jobs, forms, monitors and analytics all move with the project. From the moment of transfer, usage counts against the new workspace's plan, which must have room for the project and its custom domains. A GitHub connection moves only if the new workspace has access to the same GitHub installation; otherwise reconnect the repository after the transfer. Both workspaces' audit logs record the transfer.