Allow Devolutions Server Groups to be nested

Hello,

Thank you for your suggestion. This is not a product development that is currently planned. We’re taking note of your feedback and we will follow this topic to see if there's any additional interest or input from other users.

Best regards,

Hello,

I confirm that would be great !
For example:

You link Devolutions Server to Entra.
You have your enterprise organization represented in Entra by groups (Group MIT, Dev, Team X, Team Y,etc) with a specific naming convention which is not specifically clear/human readable.
I.E -> COMPANY_SITEA_MIT_TEAMX, COMPANY_SITEA_MIT_TEAMY

For secret you should group differently or use a clear naming convention with local DS group like:
MIT - Consultant
MIT - Support
Software - Product A

Where behind it's nested group from Entra:
MIT - Consultant -> COMPANY_SITEA_MIT_TEAMX, COMPANY_SITEA_MIT_TEAMY, COMPANY_SITEB_MIT_TEAMX
Software - Product A -> COMPANY_SITEA_SOFTWARE_TEAMX, COMPANY_SITEA_SOFTWARE_TEAMY, COMPANY_SITEB_SOFTWARE_TEAMX

Another usecase:
You need additional specific group of person which is not present in Entra but in Devolution Server -> Simply add the DS group to an existing DS group which is linked also to other Entra group.

Hello,

Thank you for the additional context, it really helps clarify the use case.

Just to make sure I understand correctly: would creating a dedicated group directly in Entra ID to wrap those existing groups be an option in your environment, and then synchronizing that group into DVLS? Or is the constraint that your Entra group structure is managed externally and cannot be modified to accommodate DVLS-specific groupings?

Understanding this will help us better assess the value of building native nested group support in DVLS.

Best regards,