RELATED IDEAS
Allow for custom layout templates to be built on other custom layouts
In our environment, we have created base custom layouts that all our teams need to use to apply standard fields common to the organization as a whole. However, most teams have a couple of additional custom fields they like to add to their workspace layout. As a result, every time we add or change a field on the base layout, we will have to manually update all of the other custom layouts - which can be over 60 layouts at times. This is a very time consuming effort and often results in errors.
It would be great if you can allow some custom layouts to be built on other custom layouts. That is, if a layout is based on another layout, the first set of fields displayed would be the fields from the base layout, and the new layout would be just the additional fields that would be display at the bottom when viewing/adding the record.
-
-
-
-
-
-
-
-
-
-
-
-
- +4
3
MERGED
Ability to define customized 'default' custom layouts for each record type that individual workspaces can then build upon
We have defined a required set of fields for every record type in Aha!. These are custom fields that are required when reporting out to our key stakeholders and executive leadership. We try our hardest to stick to a small number of custom layouts ...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved
Very much agree with that. I shared similar feedback with the customer support team; let me add it here to this chain, just to give the team a bit more context:
We have an epic template that we want to use across our workspaces. It contains around 20 fields + 10 custom fields that are shared across workspaces.
In addition to that, each workspace requires a handful (~5) of custom fields that are specific to that workspace only.
What I am seeing from the options is that I have 2 choices:
Add all custom fields to the template and enable the template for each workspace -> With our 13 workspaces, that will lead to 65 custom fields on the template (60 of which or not going to be used in the given workspace)
Create an individual template for each workspace, based on the copy/clone of the template that we already have. However, that means whenever I want to make a change to the general template and populate that across workspaces, I will need to edit 13 templates, which kind of defeats the purpose of having a template in the first place.
Here’s a suggestion that I have seen in other tools:
On the epic template, it would be great to have an additional configuration option for each field to determine in which workspace it should be visible. That enables the best of both worlds with i) being able to manage a global template and ii) still being able to cater to workspace-specific needs.