The problem
Every API key with vault access can read and write all vaults in your organization. When different teams, clients, or integrations share an account, that’s too broad.The solution
Vault groups let you:- Organize — group vaults by client, matter type, or team
- Restrict — scope API keys so they only see vaults in specific groups
- Audit — every group create, update, and delete is logged
Create a group
Endpoint
Response
The
slug is auto-generated from the name and must be unique across your organization—including soft-deleted groups.List groups
Endpoint
Response
If your API key is scoped to specific groups, this endpoint returns only those groups.
Update a group
Rename a group or change its description.Endpoint
Delete a group
Soft-deletes a group. The group must have no vaults assigned.Endpoint
Assign vaults to groups
When creating a vault
PassgroupId to place a new vault into a group:
Endpoint
Move an existing vault
UsePATCH /vault/:id to move a vault into (or between) groups:
Scoped API keys
API keys can be restricted to specific vault groups. A scoped key can only:- List and access vaults within its allowed groups
- Create new vaults in those groups (must provide
groupId) - See only the groups it has access to
Create scoped API keys in the Console under API Keys. Select the Vault service, then check the groups you want the key to access. Leaving all groups unchecked gives full vault access.

