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. Switching teams swaps the entire workspace context.
Creating and structuring workspaces
A user can create multiple teams for different labs, projects, collaborations, or client boundaries. After creation, the next operations are inviting members, assigning roles, and connecting 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 such as owner, admin, and member |
| 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. Keys are shown once at creation time and must be stored securely and revoked when no longer needed.
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.