Skip to documentation

Configuration

Workspaces and teams

Share repositories, runners, and run visibility with role-based access.

Workspace boundary

A workspace groups repositories, one registered runner, provider catalog availability, run history, invitations, and members. Switching the active workspace changes the data and controls visible in the app.

Roles

Server-side authorization and workspace row-level security enforce manager-only actions.

  • Owner: full workspace administration and ownership.
  • Admin: manage repositories, runner credentials, agents, settings, and invitations.
  • Member: view permitted workspace and repository activity without manager-only changes.

Invite collaborators

Owners and admins create invitations from Team settings. A recipient signs in with GitHub, reviews the target workspace, and accepts the invitation while it remains valid.

Frequently asked questions

Can a user belong to multiple workspaces?

Yes. Use the workspace switcher to change the active workspace.

Can members generate runner tokens?

No. Runner credentials are managed by workspace owners and admins.

What if an invitation is invalid or expired?

Ask a workspace owner or admin to create a new invitation.

Does switching workspaces stop a runner?

No. The browser's active workspace changes, while each workspace runner maintains its own connection and scope.