Template Does Not Inherit Tab Group From Host

Hello,

Thank you for your detailed report and for including the screenshots.

What you're seeing is expected behavior. Although the template is launched from a Host entry, the resulting session is treated as the template entry itself. Because of this, the Tab Group is taken from the template's own settings rather than inherited from the Host entry.

In other words, even if the Host is assigned to the Storage tab group, the session opened from the SSH template will use the Tab Group configured (or inherited) for the template. Since the template is not considered a child object of the Host for this setting, it does not inherit the Host's Tab Group.

At the moment, there isn't a mechanism to automatically apply the Host's Tab Group to sessions opened from templates. If you'd like this behavior to be supported, we would be happy to forward it as a feature request for consideration by our development team.

Please let us know if you have any other questions.

Best regards,

Hi Carl,

Thanks for the response and information. If there's currently no way to achieve this then I would appreciate if we could turn it into a feature request. I'd be open to whatever people think the best route is for this - whether it's an option to allow a host to override its templates' UI settings such as Tab Group, or something else like a variable (e.g. $PARENT_TAB_GROUP$ or something along those lines). The variable route might be more flexible to be used in other scenarios as well, and I see there are already lots of similar $PARENT$ variables like that - but if a template is not considered a child object of a host, then I suppose $PARENT$ variables might not help here. Anyway, just some ideas. As always, I appreciate the consideration.

Best regards,

Hi David,

Please submit your suggestion through our Feature Request forum. Our team can review it there.

Best regards,

Hi David,

I’m following up on Carl’s reply: there’s no need to submit a feature request for this one.

After reviewing your report, we agree with you. When a template is set to Inherited for its tab group and is opened from a Host entry, the session should use the Host’s tab group. Today, the session opened from the template is placed beside the Host in the tree, so the inheritance skips the Host entry and only looks at the folders above it. We’ve corrected that, and it will be included in an upcoming release:

• If the template’s tab group is Inherited, the Host’s tab group now applies, including user-specific settings and any variables in its name.

• If the Host itself is set to Inherited, the usual folder inheritance continues as before.

• A template with its own tab group (Custom or None) keeps it.

In the meantime, there’s a workaround: set the tab group on the folder that contains the Host entry instead of on the Host itself. Templates opened from that Host already inherit it.

Thanks for the detailed report and the screenshots; they made this easy to pin down.

Best regards,

Hello,

Thank you for your patience while our team looked into the issue you reported.

I'm happy to let you know that the latest version of Remote Desktop Manager (2026.3.16.0) includes a fix for this problem. You can download it from our website here:

https://devolutions.net/remote-desktop-manager/download/

Once you have installed the update, could you please test it in your environment and confirm that everything now works as expected? If the issue persists or if you notice anything unusual related to the same original problem, just reply to this message with a few details, and we will be glad to look into it further.

Thank you for your collaboration.

Best regards,