---
title: "Adding Portals to Record and Homepage Tabs"
slug: "adding-portals-to-record-tabs"
updated: 2026-09-18T19:06:31Z
published: 2026-09-18T19:06:31Z
canonical: "knowledge.technolutions.net/adding-portals-to-record-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.

# Adding Portals to Record and Homepage Tabs

> [!TIP]
> 🏔️ Summit 2026 Feature
> 
> Portal tabs place portal-built content directly on record and Homepage tabs, so staff can work from a customized record view. Use them to add portal content to person or dataset records without replacing the full record view.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/New person tab with type Portal.png?sv=2026-02-06&spr=https&st=2026-11-10T12%3A26%3A20Z&se=2026-11-10T13%3A26%3A20Z&sr=c&sp=r&sig=3SN%2BPvucYlxBzcaQvKC4TMl%2BXCLXJbLjizAWxwk3xYw%3D)

## Before you begin

The **Portal** list shows Express Portals with **Security** set to *User*. The portal scope must match the tab: *Person* for a Person tab, *Dataset* for a tab in the same dataset, or *User* for a [Homepage tab](/v1/docs/homepage-builder). Application-scoped portals do not currently appear in this list.

- [Create the Express Portal](/v1/docs/express-portals) to appear on the record tab.
- Confirm that the users who should see the tab [have access to the portal content](/v1/docs/portal-permissions).
- Use a portal with the same record scope as the tab. For example, a person-scoped tab uses a person-scoped portal. Staff who can view the tab can open it from the record and work with the portal content in context.

If users should enter or update mapped custom field values directly on the record, use a [form-based custom tab](/v1/docs/custom-tabs#form) instead.

## Adding a portal tab

1. Go to **Database** → **Tabs**.
2. Select **Insert**.
3. Configure the following settings:
  - **Status:** Active
  - **Name:** Enter the name that should appear on the record tab.
  - **Scope:** Select the tab scope. Portal tabs currently support *Person*, *Dataset*, and *User* (Homepage).
  - **Type:** Portal
  - **Portal:** Select the portal that should render on the tab.
  - **Order:** Enter an order value if the tab should appear in a specific position.
  - **Read Permission:** Select a permission if only some users should see the tab.
4. Select **Save**.

## Choosing portal content

A portal tab is useful when the record needs more than a simple field layout. Build the portal around the workflow staff complete from the record, such as a compact dashboard, a guided review page, or a specialized data-entry experience.

Keep the portal focused on the record context. A person-record portal should help users understand or act on the person. A dataset-record portal should focus on that dataset record's information and related actions.

> [!NOTE]
> 💡 You can [embed Searcher tables](/v1/docs/searcher-portal-record-tabs) on portals that render in custom tabs.

## Related options

To replace the standard person Dashboard tab with portal content, see [Customizing Standard Tabs](/v1/docs/modifying-standard-profile-tab-settings).

To embed a portal in Reader, see [Portals in Reader](/v1/docs/portals-in-reader).