Skip to Main Content
Status Future consideration
Categories Account settings
Created by Shannon Sauvé
Created on Feb 15, 2022
Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit A-I-10916 Allow for custom layout templates to be built on other custom layouts.

Ability to define customized 'default' custom layouts for each record type that individual workspaces can then build upon Merged

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 per record type across our organization. However, as our organization continues to grow, more and more teams are coming onboard that each have their own customization needs.

As such, the number of custom layouts defined for each record type continues to grow. Each custom layout that we create contains the same set of required fields + any custom fields for the specific team.

This leaves room for error as a field may be forgotten.

When we need to make changes to the list of required fields, we need to find every layout that is using those custom fields (which should be every layout) and the edit them one-by-one, individually.

This happens about once a quarter. It is very time consuming, error prone, and difficult to maintain.


We would ideally like to define a new "default" layout for every record type, by workspace type. The new default layout would contain our required set of fields to ensure consistency.

This would allow individual workspaces, that each have their own way of working, to add their own custom fields on top of the default layout.

This would also allow any changes made to the default template to automatically flow to every custom layout within a specific workspace type, reducing the overhead and potential for error.