RDM for teams info (asset management, licensing)
Hello guys,
I’ve been using RDM Free for years and I’m very happy with it. I’m now testing RDM for Teams with Devolutions Server (trial) because I want to centralize everything into a single source of truth.
My goal is a 2-user setup:
User 1 (technical) – connections, devices, infrastructure
User 2 (non-technical) – strictly license & asset management
For the second user I only need:
Create and edit license entries
Track expiration dates
Receive expiration notifications
No access to remote sessions, credentials, or infrastructure
My idea is:
Separate vaults per client
License entries kept separate from device entries
Permissions configured so the second user only sees/manages licenses
Previously I used ITFlow for license tracking, which worked perfect, but required duplicating data across two systems. I’d like RDM to handle everything in one place.
I’d appreciate clarification on a few things:
Is RDM Teams + Devolutions Server a good fit for this kind of separation (technical vs restricted license-only user)?
Is my approach (separate vaults + separate license entries + granular permissions) the right way to design this?
I’ve read in some places that Devolutions Server might be limited to a single user in the future. Can someone confirm if this is accurate?
If that limitation exists, what would be the recommended alternative within RDM Teams for a 2-user setup like this (SQL data source, Devolutions Hub, other architecture)?
If RDM is not ideal as a standalone asset platform, are there recommended ways to integrate it with another system (similar to ITFlow) or do you suggest a different approach altogether?
I want to make sure the architecture is clean and future-proof before purchasing licenses.
Thank you!
All Comments (4)
Hello @Valentin,
Is RDM Teams + Devolutions Server a good fit for this kind of separation (technical vs restricted license-only user)?
Yes. The Devolutions Server introduces vaults, permissions, and network integration to share access to different entries for different users.
Is my approach (separate vaults + separate license entries + granular permissions) the right way to design this?
Yes. Vaults are a great way to achieve separation of access for different users and groups.
I’ve read in some places that Devolutions Server might be limited to a single user in the future. Can someone confirm if this is accurate?
There is a version of Devolutions Server (DVLS) which is free for one user. Not sure if this is what you mean. One of the benefits of the DVLS is the network integration, like with AD domains. This allows the customer to use existing AD users and groups to access the DVLS and its resources. The domain groups can also be used for DVLS permissions assignments, which can replicate role based network access. (I do not see this being reduced to one user.)
I hope this helps you with you design choices.
Kind regards,
Kelly
Hello Kelly,
Thank you for your clarification, that helped a lot regarding vault structure, permissions and DVLS licensing model.
I don’t want to be pushy, but I’d really like to properly understand the asset management capabilities before moving forward.
Do you consider RDM + Devolutions Server suitable to be used as the main system for license and asset management? My goal is to avoid using a second platform and keep everything in one place.
If RDM is not designed to fully replace tools like ITFlow, would you recommend integrating it with another system?
Also, just to confirm: using Azure AD (Entra ID) via SAML with Devolutions Server — without on-prem AD — is fully supported, correct?
Thank you again for your help.
RDM and Devolutions Server are primarily designed for secure access management, credential storage, and centralized operational documentation. While they can certainly be used to organize and store license and asset information using structured entries, they are not positioned as full IT documentation or business management platforms in the same way as tools like ITFlow.
Because these platforms serve different primary purposes, whether RDM + DVLS can act as your “main system” for license and asset management depends on the depth and type of asset tracking you require. If your focus is secure, permission-based organization of technical information and credentials, they may be sufficient. If you require broader ITAM or business management capabilities, that should be considered in your evaluation.
Kind regards,
Kelly
Devolutions Server supports authentication with Microsoft Entra ID without requiring an on-premises Active Directory.
The recommended approach is to configure Microsoft authentication using an Azure App Registration (OpenID Connect), as outlined in our documentation here:
https://docs.devolutions.net/server/kb/how-to-articles/azure-portal-configuration-guide-microsoft-authentication/
This allows authentication to be handled entirely through Entra ID. Proper configuration of the application registration and claims is important to ensure permissions and group mappings behave as expected.
Elevate your learning - Join the Devolutions Academy !
Kind regards,
Kelly