---
title: "Custom Tabs"
slug: "custom-tabs"
updated: 2026-09-02T20:47:45Z
published: 2026-09-02T20:47:45Z
canonical: "knowledge.technolutions.net/custom-tabs"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom Tabs

You can create a home for your custom fields on the person record by adding them to **custom tabs**.

[![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/10137386668955.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/10137386668955.png)

Custom tabs are managed in **Database → Tabs**. Form tab content is managed in **Forms**, and portal tab content is managed in **Database → Portals**.

Before creating a custom tab, choose whether the tab should render a form or a portal. Most custom tabs use forms to show or update mapped custom fields. Portal tabs render portal content on the record, such as query-backed tables, Liquid markup, or other portal components. For detailed portal-tab steps, see [Adding Portals to Record Tabs](/v1/docs/adding-portals-to-record-tabs).

Custom tabs let you tailor the person record to your needs. A record can have multiple custom tabs, and through permissions, you can show different tabs to specific users. By default, custom tabs follow the standard Materials tab in alphanumerical order.

Custom tabs can add value by:

- Enabling users to enter information directly on records
- Displaying information directly on a record rather than through a separate dashboard
- Using custom fields for entering and displaying custom information
- Providing messages automatically across staff populations

Follow these steps to choose a tab type, prepare the form or portal content, and create the custom tab.

## Custom tabs for Student Success

[Embedded content](https://player.vimeo.com/video/787681176)

The standard tabs included on the person record include the Dashboard, Timeline, Profile, and Materials. In order to display additional information on a person record, custom tabs will need to be created. Depending on the desired display of information, multiple options are available to display data.

### Entities

[Entities](/v1/docs/entities-overview) provide an easy-to-read display for objects that have a "one-to-many relationship" in Slate. One example is displaying a student's multiple scholarships on one tab.

[![Custom Tab Entity](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/custom_tab_entity.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/custom_tab_entity.png)

### Form tab data display

When a custom tab renders a form, the default display shows fields in a stacked or table format, just as it does on a standard form.

[![Custom Tab List](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/custom_tab_list.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/custom_tab_list.png)

## Custom tabs for Advancement

**Custom tabs** can be created for constituent and dataset records.

[![Custom Tabs](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/83kzehsaxk6gd5azvvpiqmceclip0.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/83kzehsaxk6gd5azvvpiqmceclip0.png)

Custom tabs can display the data you want to appear on constituent or dataset records. Form tabs can also be used to enter data directly in custom fields.

By default, custom tabs appear in alphanumeric order to the right of the standard **Materials** tab. Permissions on custom tabs determine visibility for only specific users.

## Best practices for custom tabs

Following these tips will give you the best custom tab experience:

#### Less is more

To keep things clean and easy to navigate, only add fields to custom tab forms that you'll use or update often. Limiting the number of custom tabs makes it easier to find what you need without getting overwhelmed. Keeping these concise and easy to view will also help with editing data.

#### Use conditional logic filters with merge fields, not form fields

When you add a conditional logic filter on a custom tab form field that’s not visible to the internal user, you risk overwriting the data in these fields with null values.

Avoid overwriting data by using conditional logic on **merge fields** on custom tabs; merge fields can only ever display, but not write, data.

#### Displaying dates on custom tabs: date versus calendar

By default, form fields with a type of **Date** store data using a `yyyyMMdd` format*.* For example, `20220225`.

Form fields with a type of **Calendar** store data using a `yyyy-MM-dd` format. For example, `2022-02-25`.

To populate the selectors when interacting with these type of fields on a custom tab, Slate requires storing the underlying data in the associated format.

Be consistent about which form field type you use on these tabs. Ensure that the date values are being imported or collected in the associated format for that type.

Alternatively, display dates on your custom tab with [merge fields on forms](/v1/docs/merge-fields-on-forms).

#### Use merge fields for read-only information

If you need to show read-only data on custom tabs, use [merge fields](/v1/docs/merge-fields-on-forms#displaying-name-information-0-0).

Merge fields let you display data that should not—and cannot—be edited. Using merge fields instead of selecting *Read Only* on a field ensures it cannot change or be overwritten.

#### Default value form fields

Generally, default values populate when a form loads. This default value will be saved when the form is submitted unless the value is changed.

If a value is previously stored in a particular field for which a default value is set, submitting the form with the default value will either update or append the previously stored value. The very nature of a default value is such that it will always suggest a particular value for a field on a form.

Because of this functionality, do not use default values on custom tab forms. The primary purpose of these types of forms is to *display* the values stored in a particular field.

## Step 1: Choosing the tab type

Before creating the tab, decide whether the tab should render a form or a portal.

#### Form

Select this type when users should view or update mapped custom field values directly on the record. A form tab uses a **Person Page**, **Application Page**, or **Dataset Page** form.

#### Portal

Select this type when the tab should render portal content, such as query-backed tables, Liquid markup, or other portal components. Create the portal before creating the tab, and build the portal for the same record context as the tab scope.

📖 More information: [Adding Portals to Record Tabs](/v1/docs/adding-portals-to-record-tabs)

If you choose **Form**, continue with Step 2. If you choose **Portal**, create the portal and then skip to Step 3.

> [!WARNING]
> 📝 If you want this tab to have [subtabs](/v1/docs/subtabs), this option must be left blank.

## Step 2: Preparing a form tab

Create a form only when the custom tab type will be **Form**. For portal tabs, skip this section.

For a form tab, first make a list of the custom fields needed on the tab. For example, for a *Details* tab, you might include:

- Academic Interests
- Entry Term
- Extracurricular Interests
- Language 1
- Language 2
- Music Interests

Next, decide the order of the fields, and which fields should be grouped together. For the same *Details* tab:

- **Interests Group**
  - Academic Interests
  - Entry Term
  - Extracurricular Interests
  - Music Interests
- **Languages Group**
  - Language 1
  - Language 2

To build the form, take the following steps:

1. Go to **Forms**.
2. Select **New Form**.

Configure the following settings:
  - **Page Title:** Enter a straightforward name, such as "Details Custom Tab."
  - **Folder:** Create a "Custom Tabs" folder to keep forms organized.
  - **Status:** Set the status to **Confirmed/Active**.
3. Select **Save**. With the form created, select **Edit Form**.
4. Select **Edit Properties**.
5. Set the form scope for the tab:
  - For a person record tab, select **Person Page**.
  - For an application record tab, select **Application Page**.
  - For a dataset record tab, select **Dataset Page**, and then select the correct dataset from the **Dataset** list.
6. Remove all of the standard Slate fields included on the form by default, such as name and address fields.
7. Add custom fields to the form. **Custom tab forms must only contain fields that are mapped to custom fields.**

To further enhance the look of a custom tab form, group fields together in sections by adding header rows.

[![Form](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/form.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/form.png)

Select compatible field types from the Form Builder palette for mapped custom fields. For example, a custom field using prompts should be added using a form tool that supports prompts (such as a Select List).

[![Custom Tab](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/tu9ggmfgdkwe3psopiwwmceclip6.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/tu9ggmfgdkwe3psopiwwmceclip6.png)

## Step 3: Creating the custom tab

After the form or portal exists, create the tab and select the type of content that should render on the record.

1. Go to **Database** → **Tabs**.
2. Select **Insert**.
3. Configure the following settings:
  - **Status:** Keep this setting set to **Active** for the tab to appear on records.
  - **Name:** Enter the name that should appear on the tab when viewing records.
  - **Scope:** Select **Person**, **Application**, or **Dataset**. For dataset tabs, select the correct dataset after selecting **Dataset**.
  - **Type:** Select **Form** or **Portal**.
  - **Form:** If the type is **Form**, select the form that should render on the tab. The list contains forms with the corresponding page scope, such as *Person Page*-scoped forms for a person-scoped tab.
  - **Portal:** If the type is **Portal**, select the portal that should render on the tab.
  - **Order:** Custom tabs are ordered alphabetically by default. To override the alphabetical order, enter an order value for the custom tab.
  - **Read Permission** *(Optional)*: Select a read permission for the tab. Users without the selected permission cannot see the tab.
  - **Write Permission** *(Optional)*: For form tabs, select a write permission if only some users should be able to edit data on the tab.
  - **Show for Records in Population** *(Optional)*: Select a population if the tab should appear only for records in a specific population. This setting does not apply to dataset tabs.
  - **Notes** *(Optional)*: Enter internal notes about the tab.
4. Select **Save**.

The custom tab will now appear on records that match the tab scope and visibility settings.

## Administrative experience

#### Custom person and dataset tabs

After configuration, person and dataset-scoped custom tabs appear on the record to the right of the standard tabs. To add, remove, or reorder custom fields on a form tab, edit the custom tab form. To change content on a portal tab, edit the selected portal.

[![Custom Tab](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/custom_rec.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/custom_rec.png)

#### Custom Application Tabs

Custom application tabs links appear on a record's application tab on the right-side pane.

[![Custom Application Tabs](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/custom_app.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/custom_app.png)