Layout artifact
RDM Vault Layout Map for Shared Teams
Use this independent vault layout map to decide where Remote Desktop Manager connection entries, credentials, documentation, and privileged access notes should live before a team imports more data.
This site is independent and is not affiliated with, endorsed by, or sponsored by Devolutions. Remote Desktop Manager is referenced only to describe compatible workflows.
Vault layout decision matrix
| Workspace area | Recommended boundary | Review signal |
|---|---|---|
| Shared infrastructure | Servers, routers, hypervisors, and cloud consoles grouped by operating team | Every entry has an owner and escalation note |
| Privileged credentials | Break-glass and admin credentials separated from daily connection entries | Access is reviewed on a fixed schedule |
| Client or department vaults | MSP client groups or internal departments separated by support responsibility | Technicians only see the workspace they need |
| Session documentation | Notes, runbooks, and handoff context attached near the connection path | New staff can understand usage without asking the last owner |
Pre-import checklist
- List the data source that will hold shared entries and confirm who administers it.
- Mark entries that contain privileged credentials before importing them into a shared vault.
- Define naming rules for servers, cloud consoles, VPN profiles, and database sessions.
- Write a short access note for each team or client group so permission changes are easier to audit.