Teams
Manage the workspace itself: members, roles, invitations, secret keys, and integrations.
A team is the workspace boundary in VOLT. Trajectories, clusters, containers, notebooks, chats, LaTeX projects, AI providers, secret keys, and permissions all belong to a team, and switching teams swaps the entire workspace context.
Creating and structuring workspaces
Create multiple teams to separate labs, projects, collaborations, or clients. After creation, you invite members, assign roles, and connect infrastructure.
Invitations
VOLT supports two invitation styles:
- Email invitations provide a traceable flow with pending status and cancellation controls.
- Invite codes provide a faster, lower-friction path.
Both produce the same result: the new member joins the team and inherits the permissions assigned by their role.
Roles and RBAC
The team module includes an RBAC layer that maps roles to specific resources and actions.
| Role Type | What It Means |
|---|---|
| System roles | Built-in roles: owner, admin, member, and viewer |
| Custom roles | Team-defined roles with targeted permission sets |
Secret keys and programmatic access
Teams issue secret keys for API and SDK access through tools such as voltsdk or @voltstack/voltclient. Each key is assigned a team role and inherits that role's permissions, so keys can be scoped to exactly the access required. Keys use a vsk_ prefix and are shown once at creation time; only a prefix and hash are retained.
Team secret keys grant programmatic access to the workspace. Store them securely, rotate them when needed, and revoke them on suspected exposure.
AI integrations
Volt AI provider management is part of team administration: provider keys, model availability, and AI configuration belong to the team, not to individual user profiles.