GUIDE
Structure a team vault
A practical introduction to structuring resources, separating environments and keeping versions in a team vault.
Read the guideResources
Practical guides to team vaults, access permissions and the MyVaultDesk MCP connector.
RESOURCES
GUIDE
A practical introduction to structuring resources, separating environments and keeping versions in a team vault.
Read the guideGUIDE
Understand roles, consultation permissions and access reviews in a shared MyVaultDesk workspace.
Read the guideGUIDE
Understand the role of the MyVaultDesk MCP connector and how workspace permissions apply to assistant requests.
Read the guideRESOURCES
Technical credentials, API keys, certificates and connection details. Vaults group these resources by project or environment.
Project vaults keep production and staging resources separate. Use the environment tabs in the interactive preview on the Product page to see the difference.
Access depends on the teams and consultation permissions assigned to the vault. The Product page illustrates separate access for production and staging.
The connector provides a route for development assistants to consult resources authorized by the team. The Integrations page explains the link between the assistant, permissions and resource.
Resources keep their previous versions alongside expiration dates and renewal reminders. The activity history records consultations, changes and access.
Use the workspace link provided by your administrator. You can also open the application portal using Sign in at the top of this page.
Find your team’s vaults and authorized resources in the MyVaultDesk application.