Workspaces and members

An organization has admins and developers. A workspace membership has no separate role. Admins manage every workspace in their organization, and developers use the workspaces they belong to. Each developer member has one workstation in a workspace, and only its owner can open it, connect over SSH, or start and stop it.

​

Create a workspace

Open Organization, then Workspaces, and choose Create workspace. Give it a name, then open its settings to configure tools, resources and policies. Admins manage workspaces but cannot join them as workspace members. A workstation is for a developer member. The API refuses an attempt to add an admin with Admins don't join workspaces. Change their role to developer first.

​

Add members

Invite people from the organization’s Members page and choose their role and workspaces. To add an existing organization member to a workspace, open that workspace’s Settings, then Members. KolaOS queues a workstation when a developer joins a workspace through an invitation or when an admin adds them. Each member can have at most one workstation in a workspace. Capacity, infrastructure and plan errors remain visible until resolved.

​

Workstation permissions

Preview sharing gives access to the shared port within the workspace policy. It does not give access to the owner’s IDE or SSH session. The API and gateway enforce workstation access outside the workstation. A restriction inside a workstation or on a laptop only deters, because the developer has root there.

​

Remove access

Remove a member from a workspace to end their access and stop their workstation. The workspace retention setting controls when the removed member’s workstation is deleted. Removing a member from the organization ends their organizational access. Deleting a workstation does not automatically queue a replacement. Only admins can delete one, and deletion removes its work. Keep needed changes in your repository before deletion. An organization must keep at least one active admin. You cannot change your own role or offboard yourself, and a change that would remove the last active admin is refused.