Workspaces & team management
Introduced in v1.14.0
A workspace is the container for everything you deploy on ZaneOps: projects, services, environments, Git apps and registry credentials all belong to a workspace.
Every ZaneOps instance starts with a single workspace, created during onboarding and owned by the first user. From v1.14 you can invite other people into a workspace and give each of them a role that decides what they can see and do.
Each member of a workspace has exactly one role. Roles are cumulative: every role can do everything the role below it can.
| Role | What they can do |
|---|---|
| Viewer | Read-only access. Sensitive fields (environment variables, secrets, tokens) are hidden. Access can be restricted to specific projects. |
| Member | Everything a Viewer can do, plus: edit service configuration, create/update/delete environment variables, trigger deployments. Sees all projects in the workspace. |
| Admin | Everything a Member can do, plus: delete services, invite and remove members, change roles, manage API tokens. Cannot delete the workspace. |
| Owner | Everything an Admin can do, plus: delete the workspace and transfer ownership. Each workspace has exactly one Owner. |
Inviting people
Section titled “Inviting people”Admins and the Owner can invite users from Settings > Team.
-
Go to Settings > Team and choose Invite user:
-
Enter the person’s username, pick a role, and (for a Viewer) select which projects they may access:
-
ZaneOps generates an invitation link. Send it to the invitee.
- If they already have an account on this instance, opening the link adds them to the workspace immediately.
- If they don’t, the link lets them create an account and join in one step.
Managing invitations
Section titled “Managing invitations”From Settings > Team > Invitations you can:
- Regenerate an invitation link (invalidates the previous one)
- Revoke a pending invitation
- See which invitations have expired (invitations have a limited lifetime)
Managing members
Section titled “Managing members”The Team page lists everyone in the workspace with their role. Admins and the Owner can:
- Change a member’s role
- Edit a Viewer’s project access
- Remove a member from the workspace
Leaving a workspace
Section titled “Leaving a workspace”Any member can leave a workspace from their account menu. The Owner cannot leave; they must first transfer ownership to another member.
Transferring ownership
Section titled “Transferring ownership”The Owner can hand the workspace over to another member from Settings > Team. After the transfer, the previous Owner becomes an Admin.
Switching workspaces
Section titled “Switching workspaces”If you belong to more than one workspace, a workspace switcher appears in the top navigation. Switching changes the projects, services and settings you see; it does not log you out.
Server administration
Section titled “Server administration”Some actions live outside any workspace, in the Server admin area, and are reserved for the instance owner (the first user of the instance):
- Users: every account on the instance, password-reset links
- Workspaces: create, inspect and manage all workspaces and their members
- Jobs & schedules: cron schedules and retention policies for Docker pruning and log/build-cache cleanup
- Global HTTP logs: every request that went through the ZaneOps proxy, across all workspaces, with the country it came from
- License: install, view or remove the instance license
- SSH keys and the server terminal
