Custom layouts

Aha! Discovery

To create and edit custom layouts, you need to be an Aha! Discovery administrator with customization permissions. To choose which layouts to use for a workspace in your account, you will need workspace owner permissions.

Click any of the following links to skip ahead:

Create a custom layout

Records in Aha! Discovery come with a default layout of standard fields. If you want to customize the layout of a record's fields, you should create a custom layout and apply it to your workspace.

There are two ways to create a custom layout (or adjust an existing one):

  • On the More options button on a contact or organization, select Create new custom layout or Edit custom layout. Either option will open the Custom layout builder.

  • Navigate to Settings ⚙️ → Account → Custom layouts. Select the record type you want to adjust, then click Add custom layout or hover over a layout you wish to Edit. Either option will open the Custom layout builder.

With the Custom layout builder open, start by giving your custom layout a Name.

Top

Customize a record's layout

Users will see a record's layout after it has been created. They can access a record either in its full-page Details view or in a pop-out Drawer view while they are on the Participants page.

Adjust layout fields

The Fields list on the left shows you all available Existing custom fields you can add to your layout (with a search bar to help you sort through the list). If you realize at this point that you want to create a New custom field, you can do that as well. In either case, drag the field you want to add over to your layout. If you are creating a new field, you will be asked to name it and provide any other details relevant to that custom field.

Is your list of existing custom fields full of discarded and duplicate fields? In Settings ⚙️ → Account → Custom fields, you can merge duplicate fields or convert a custom field from one type to another.

You will see an example record in the center of the page with a few default fields to get your layout started. First, configure the fields you see in the Overview tab.

  • Add fields: Drag standard or custom fields from the Fields list to your record layout to add them. Or drag them off the record layout to remove them.

  • Remove fields: Click the More options button beside a field and select Remove from layout to remove it.

  • Rearrange fields: Drag fields in your layout vertically to rearrange them.

  • Adjust field visibility: Use the More options button beside each field to decide whether that field should be Always shown when a user first opens the record, Hidden, or (where available) Hidden if empty. Users can always expand a record's layout to show a full list of fields, so you want to make sure that the fields most commonly used in your record workflow are always visible.

  • Mark fields read-only: Use the More options button beside a field to mark it read-only.

  • Edit custom fields: If you need to adjust a custom field that you added, click the More options button beside the field and select Edit custom field.

Adjust layout tabs

Next, configure how tabs are arranged on a record's layout.

By default, a record's Overview will be the first tab in the drawer view and a collapsible column on the right side of the details view. You can also see a tab for all records Related to the record and a History of all changes to the record.

  • Click and drag tabs to rearrange their order.

  • The Details view of a record layout includes a right sidebar. By default, the Overview tab takes this position, but you can move any tab into that sidebar. You can also choose not to place a tab here and have a layout without a sidebar.

  • A custom layout can show several tabs side by side, depending on the size of your browser window. The More tab is an overflow space where tabs beyond what your browser window can show appear. Use the More tab in the layout builder to select which tabs should be hidden behind the More tab if a user's browser window cannot fit all the tabs in one view.

Finished? Great! Look to the top-right corner.

  • If this is an existing layout applied to a workspace, hover over the Impacts # workspaces link to see what workspaces changes to this layout will affect. Then, click on any individual workspace to see more details. Multiple workspaces can use the same custom layout.

  • Use the view buttons to switch between the Record view layout's Drawer and Details views.

  • Click Cancel to cancel your changes.

  • Click Save layout to save your layout.

Top

Mark fields read-only

Custom layouts highlight critical information through fields and tabs — but sometimes, you do not want your team to update that information.

Read-only fields block anyone from updating the field through a record's drawer or details view. This ensures users in your Aha! account have the proper context, but cannot accidentally adjust fields that need to stay static. Read-only fields are not locked fields, however. They can still be updated through the Aha! API. This is often the key to read-only fields' true value: The right people can update them, and everyone can benefit from their information.

To mark a field as read-only, click the More options button beside it in the layout builder and select Read-only. Once you Save your layout, the field you marked read-only will be immediately uneditable within the record's detail or drawer view.

Top

Apply custom layouts to your workspace

To apply an existing custom layout to your workspace, navigate to Settings ⚙️ → Workspace → Configure → Custom layouts. Select the layout you want to use and whether it should inherit a layout from a particular parent line. This is useful for driving layout consistency across your workspace hierarchy.

Note: A record will only display the custom fields that are included in the Record view layout of the workspace where the record resides. For example, you could create a record in Workspace A and then move it to Workspace B, which uses a different layout. For the same data to be visible in Workspace B, the layout for Workspace B must include the same custom fields that were defined in Workspace A.

Top