Documentation
Workspace
Teams, permissions, and billing
Shape workspace access and capacity without sharing provider ownership credentials or losing visibility of existing resources.
Updated Jun 22, 2026
2 min read
What workspace controls do
Teams, permissions, and billing controls shape who can operate infrastructure and how much capacity the workspace has. The goal is to avoid sharing provider ownership credentials while still letting the right people work safely.
Before inviting a team member
- Decide which workspace they should join.
- Choose the smallest useful role or custom permissions.
- Confirm whether they need provider, server, site, billing, team, or settings access.
- Plan when access should be reviewed or removed.
Typical workflow
- Invite the team member.
- Assign a role or permission set.
- Confirm workspace switching points at the right owner context.
- Keep billing-sensitive settings owner-aware.
- Review usage against plan limits before creating new resources.
Checks before expanding a workspace
- Existing servers and sites remain visible when limits change.
- Downgrades do not imply deletion of resources.
- Billing changes are confirmed through Stripe.
- Admin access does not accidentally include ownership credentials.
- Viewer access remains read-only for infrastructure and integrations.
Common issues
- A contractor keeps access after their work ends.
- A team member needs deployment access but is given broader server permissions.
- Resource limits are hit during a launch because capacity was not checked.
- Billing ownership is unclear when a client or agency changes responsibility.