RELATED IDEAS
Option for workspace template to not override all settings when first applied
What is the challenge? |
When applying a workspace template, even if the settings are marked as unlocked in the template, once applied to a workspace the existing workspace settings will still be changed. This is not always the desired experience. If I have a field unlocked, I may want that team to maintain their current customization (for example, their custom terminology). |
What is the impact? |
The template always overriding settings (like layouts) means that applying a workspace template can involve a lot of change management for current teams. They will need to go back in and update their workspace settings to re-add their customizations. If I just want a few settings maintained across workspaces, a template does not make this easy and will cause unwanted settings updates. |
Describe your idea |
Setting on workspace template to set specific areas to not override existing settings when applied. |
-
-
-
-
-
-
-
-
-
-
-
-
-
- +4
© 2025 Aha! Labs Inc.•All rights reserved
Each workspace shares a similar configuration, but certain records are set up differently. It would be extremely helpful to have an option that allows me to selectively apply specific fields from my workspace template to other workspaces. For example, automation rules for our Ideas Portal are consistent across all workspaces, and we use the same portal throughout. Having the flexibility to choose which configurations to replicate—such as automation rules—would streamline setup and ensure consistency where needed, without overwriting unique workspace-specific settings.
Since established scorecard values will be lost if the destination workspace scorecard configuration differs from the template scorecard configuration, this prevents us from moving pre-existing workspaces onto our template - which increases our workload every time we want to roll out any template based automation, etc. and effectively defeats the purpose of even having a template.