Team vaults
This page explains how Termius organizes shared access to infrastructure using vaults. It covers vault structure design, managing members and permissions, and moving data between vaults.
Overview
Team vaults are the top-level organizational unit in Termius. A vault stores data and controls which team members can access it.
Each vault is encrypted with a unique key. Members can access a vault only after the owner grants them permissions.
To start collaborating in Termius invite your team members. Learn more in Team Management.
Termius includes one non-shared Personal vault per user, and one default Team vault shared with all team members. Additional custom team vaults can be created and shared with specific team members.
Members can have different permissions in different vaults:
Can edit: Allows creating, updating, and deleting data within the vault; adding or removing members.
Can view: Allows viewing data, initiating connections to hosts, and running snippets. Data cannot be modified.
Create vaults
Define the vault structure
Whether you separate access by projects, clients, environments, departments, or other criteria, vaults can be configured for that use case.
A few examples of how different teams organize their data using vaults:

The team structure is flat, with a small number of members and a high level of trust.
Vaults: A single Team vault shared with all members
Groups: Prod, Staging, and Development

The team structure is client-based, where small teams or individuals work with several clients.
Vaults: Each client has a separate vault. Team members are added and removed from vaults depending on the projects and clients they work with
Groups are used to separate environments within the client's vault

The team structure is functional-based, with dedicated DevOps, Developers, and QA teams.
Vaults: Vaults separate Production, Development, and Staging environments. DevOps has access to all three. Developers can access Staging and Dev, while QA can only access Staging
Groups: Within each vault, there are groups for different resource types, such as Database Servers (DB), Web Servers, and Cache

The team structure is functional and location-based, with infrastructure distributed across multiple regions. Access is organized by region or data center.
Vaults: Organized by region and team. For example, US-East-DevOps, US-East-Support, US-West-DevOps, EU-Central-DevOps
Each team structures groups to match their operational context. A data center team, for example, might organize by physical location: building, floor, room, and rack
Add custom team vaults
To create a new vault, you have several options:
Open
Settings>Vaults>Add vault
Click the chevron on the
Vaulttab and clickAdd vault
Click the
Vault selectoron the entity edit form and clickAdd vault
Name it according to your vault structure

Add members to this vault and set their roles

Click
Save changes
Add data to vaults
To add data to a vault, you have several options:
Open entity details and click the
vault selectorto choose the vault to move it to
Right-click on an entity you want to move or copy, then select
Move toorCopy toand select the destination vault
Choose where you want to store credentials for hosts and groups

Personal vault — the host or group will be added to a vault without credentials. Each member will need to use their own set of credentials saved in their Personal vault
Selected vault — the host will be added to a vault with credentials. Each member will connect using the same shared credentials. Once the entity is saved to this vault, it is instantly accessible by all team members with access
Once an entity is moved or copied, it is immediately available to all members of the selected vault
If the selected entities have linked entities, choose how to handle them:
Copy — all linked entities are copied to the selected vault and also remain in the original vault
Move — all linked entities are moved to the selected vault, removed from the original vault, and unlinked from all other entities in the original vault

Edit vaults
Change vault name
Open
Settings>Vaults, or click the chevron on theVaulttab and clickManage vaults
Select a
vaultyou want to edit. Personal and Team vaults have default names that can't be changed
Click on the vault name and change it
Click
Save changes
Add members
Open
Settings>Vaults, or click the chevron on theVaulttab and clickManage vaults
Select a
vaultyou want to edit
Add team members to this vault from your team and set their roles

Click
Save changes
Change member permissions
Open
Settings>Vaults, or click the chevron on theVaulttab and clickManage vaults
Select a
vaultyou want to edit
Click the
permission pickerfor the member you want to edit:Can edit allows the member to edit entities in the vault
Can view allows the member to connect and run snippets, but not edit them
Remove access allows removing a member from the vault

Click
Save changes
Open the
Vaultspage on the account management portalSelect a vault where you want to change a permission

Click the
permission pickerfor the member you want to edit:
Can edit allows the member to edit entities in the vault
Can view allows the member to connect and run snippets, but not edit them
Save changes
Remove member from vault
Open
Settings>Vaults, or click the chevron on theVaulttab and clickManage vaults
Select a
vaultyou want to edit
Click the
permission pickerfor the member you want to remove and selectremove access
Save changes
Security
Vaults are the most secure way to share sensitive information across the team. Each vault is encrypted with a unique key, so only you and your team members with access to that vault can see and use its data.
New members cannot access a vault until the owner grants access and sets their permissions.
For more information about encryption and security, see Encryption overview.
Last updated
Was this helpful?

