Team Workspaces & Permissions

Not in release builds yet

Team workspaces are built, but release builds of Server Compass (v1.45.0 included) keep them switched off, so there is no Team tab in the sidebar yet. This page describes how they work once a release turns them on. Watch the changelog for that release.

What Team workspaces do

Team workspaces let you "share infrastructure access without sending credentials in chat." A server's SSH credentials move into an encrypted, storage-backed workspace, and you scope per-member access from there. Once enabled, open it from the sidebar's Team tab. Team requires an active Pro license. Without one: "Team workspaces require an active Pro license. Existing shared data stays visible, but mutations are read-only."

Create or join a workspace

Use New workspace or Join. The dialog asks for:

• Workspace name
• Recovery passphrase (at least 12 characters)
• Your display name
• Invite code (a full SCTW1 code, when joining)
• Storage destination

Storage must be S3-compatible — "conditional writes are what stop two people from overwriting each other." SFTP, Google Drive, and pCloud cannot host a Team workspace.

Roles and per-server grants

Workspaces have four roles: owner, admin, member, and viewer. Owners and admins inherit every shared server and cannot be narrowed per server; members and viewers get explicit grants. On the Permission tab ("Who can reach which server"), Share a server moves its SSH credential into the encrypted Team vault. Choose a share mode — Use only or Use and reveal — then grant access in the matrix: Whole server or individual apps, with an optional Expires time. "Grants are checked at every action. Desktop, remote, and MCP all honour expiry."