Tag inheritance

Hello,

This was requested in the past in the following thread, so we will note your interest for this feature.

Regards,

Hi,
any news regarding this feature request? We would really appreciate this functionality.
Thanks.

BR,
Martin

Hello Martin,

Nothing new for now but I encourage you to upvote the thread so we can more easily see user interest for this feature.

Regards,

Hello @timhauptmann and @martindvorsky ,

We're currently working on implementing a configuration to allow inherited tags. I had one question for you regarding this part:

with the option to deactivate this per entry

At the moment in our internal development, we can configure this in the vault or the system settings, so that administrators can have this apply to specific vaults, or to their whole system more easily. We didn't want to complexify configurations more, so we were opting to not have it be configurable in entries (folders or sessions) directly.
Is being able to deactivate this per-entry something crucial for the environment you're trying to configure? If it is, we will have to adjust our solution.

Regards,

Hi Hubert,
in my case it would be a nice-to-have feature, but it isn't a show stopper. We can make a workaround, for example create a separate entry (not subentry) when we don't want to inherit tags.

BR,
Martin

Hello,

Thank you for the feedback.

We can make a workaround, for example create a separate entry (not subentry) when we don't want to inherit tags

That's correct, this would work as long as the entry isn't in a folder where the folder or its parent folders contain tags. If they do, then this entry would also have the tags belonging to these folders.

For now, we will stick to having it be configurable at the vault and system setting levels. As usual, we are open to feedback, and if we (or our users) realise that having this granularity would be beneficial despite complexifying the configuration, then we will add it.

Regards,

Hello, just curious, is there a way to apply tag inheritance to all entries within a folder? (perhaps including subfolders themselves as well)?

And to somehow make that the case for new entries that would be added to the folder in the future?

I see we can add tags and they seem to be inherited, sometimes, but other times not. I don't really understand it. In Edit -> Tag Management, we can check/uncheck which entries/folders they're applied to, but I don't see a way to check a folder and auto-apply to everything below it?

Edit - there is just a "check all" and "uncheck all" option to select/unselect the entire tree for a tag but that's it. No way that I can see to select a folder and it's child objects. This is in v2025.3.20.

Any help is appreciated!

Best regards,

Hello David,

Tag inheritance as a feature came out in 2026.1 so there's nothing really available in 2025.3 for this.

In 2026.1, you can configure either at the vault level or at the system settings level what the inheritance system for this vault or for the datasource is. Here's what it looks like at the vault level, which you can see by editing the vault's settings:

By default, in the vault's settings, it will check at the system settings level. This allows you to set something by default for your whole data source, and then change it for certain vaults which should not use the same value.

The "Custom" mode is the same one that's always existed, while the "custom + inherited" mode is the new mode introduced in 2026.1. This new mode makes it so if a tag is set in your folder, entries within that folder will automatically possess this tag as well. This also applies to subfolders.

We decided not to allow changing this setting at the folder level to keep the settings as simple as possible, but as I mentioned in my previous message in this thread, if this is a need for our users, we will add it.

I would recommend you trying out 2026.1 and this setting to feel it in action and see if it works for your needs. Keep in mind if you're using a team data source like Devolutions Server or SQL Server, a database upgrade will be required and from there it will not be recommended to downgrade your RDM as it may cause incompatibilities. You could always try it out on a portable version with an SQLite datasource if that's a concern, as the feature is also available there in the vault settings.

Regards,

Thanks for the details Hubert! I will plan an update to v2026.1 with our team so we can try out the new feature. Just thinking ahead, I could see where the ability to override the inheritance rule on a specific folder (e.g. so majority of subfolders/entries would inherit tags, but specific folders and/or entries may not) could be useful, but I will try it out as-is first for a while and then post back here with feedback/results 🙂

Best regards,

Hi @Hubert Mireault ,

Just have a quick related question, I just upgraded to v2026.1.16 and am checking out the tag functionality. I notice for some reason, when I edit the tags on a template, it doesn't seem to make available all the tags I've been using on other objects (like entries or folders)?


When I edit tags on an entry, I see all existing tags in the list that are in use anywhere, and I can choose one/multiple of them or add a new one. But when I do the same on template, I get the empty list - I can add new tags to the template, which I did, but then even if I edit another template I don't even see the ones I just added to the first. It's as if every template has its own independent set of tags. Is this by design or a bug?

Best regards,

Hello David,

I'm not fully sure how the code was implemented for the tag prompt. Whether it's a bug or a missing/unclear feature, I think it's something we should look at regardless. I will open a ticket for this.

Usually, it lists a combination of the tags configured in the system settings as well as the tags on entries in the current vault. I would have thought that since in the code, the templates are in their "own" vault, perhaps it would only show tags from that "vault", but it doesn't seem to be the case either.
We'll have to see what we can do to improve this but it definitely should not list nothing.

Regards,