Bug: Vault templates do not apply permissions to sub-entries (folders/items) when creating a new vault

Hi Devolutions team,
I’ve encountered an issue with vault templates in Devolutions Hub / Cloud.

Steps to reproduce:

1. Create or edit a Vault Template.
2. Configure specific access permissions (granular rights) on sub-entries (such as folders or specific items) for custom user groups or users within the template.
3. Create a new vault based on this template.

Expected behavior: The new vault should inherit the exact sub-entry permissions (folder/item-level access control) defined in the template for the specified groups and users.

Actual behavior: While the vault is created from the template, the custom permissions configured on the sub-entries are not applied. The folders/items end up without the intended group rights, requiring manual reconfiguration for every new vault.
Could you please look into this? Let me know if you need any logs, screenshots, or additional details.

Thanks,