> For the complete documentation index, see [llms.txt](https://docs.scaleflex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scaleflex.com/portals/all-portals/settings/default-portal.md).

# Default portal

Send visitors straight into one Portal instead of showing them the Portal list.

By default, someone who opens `https://portals.scaleflex.com` or your own custom domain sees the list of Portals in your project. Setting a default Portal sends them straight into it instead.

Use it when your project has one Portal that is the front door: a brand hub, a press room, the Portal your custom domain exists for.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FYY0tHdrAmlEbX8OTf0Mj%2Fimage.png?alt=media&#x26;token=7f4c93cd-1b4f-4620-b504-f02dd030a725" alt=""><figcaption><p>The Default Portal card, on the project's Settings page.</p></figcaption></figure>

## Set the default Portal

1. Open **Settings**.
2. Find the **Default Portal** card.
3. Choose a Portal from the list. Start typing to search if the project has many.

The change takes effect immediately; there is nothing to save or publish.

To stop redirecting and show the Portal list again, choose **No default portal**, or clear the field with the **×**.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2F5fHGPXsjP7eXsTwqPr6W%2Fimage.png?alt=media&#x26;token=3ebeed56-13c2-4157-9436-45963556d8e4" alt="" width="375"><figcaption><p>Choosing which Portal to send visitors to.</p></figcaption></figure>

## Which Portals you can choose

The list covers the Portals in the current project, excluding templates and archived Portals.

## The Portal must be published

A default Portal only takes effect once it is published. Choose an unpublished one and the settings card warns you:

> This portal is not published yet, therefore visitors will not be redirected here until it is.

Until then, visitors see the Portal list as before.

## You can't archive the default Portal

Archiving is blocked while a Portal is the project default, so nobody can accidentally break the redirect:

> This is your project's default portal. Change the default portal in Settings before archiving it.

Choose a different default or **No default portal,** and then archive it.

## A default per custom domain

If you use custom domains, each one can open its own Portal. A project running several audiences from one set of assets can give each its own address:

| Address                 | Opens                        |
| ----------------------- | ---------------------------- |
| `portals.scaleflex.com` | The project's default Portal |
| `pro.example.com`       | The Professional Portal      |
| `shop.example.com`      | The Retail Portal            |

### Set a default Portal for a custom domain

The default you set belongs to **the address you set it from**. So to give a custom domain its own Portal, open the settings page on that domain rather than on `portals.scaleflex.com`.

1. Go to `https://<your-custom-domain>/portals` and open **Settings**.
2. Check the note on the **Default Portal** card. It names the domain you are on:

> You're viewing this page on the custom domain \<domain>. Setting a default portal here will be prioritized when visiting https\://\<domain>.

3. Choose the Portal that domain should open.

Repeat on each custom domain you want to point somewhere of its own.

{% hint style="warning" %}
If that note is missing, you are on the main domain and are setting the **project** default instead — which will not change where any custom domain lands.
{% endhint %}

### What happens when there is no default

A custom domain with no default Portal of its own does not fall back to the project default. Visitors arriving at its bare address are sent to the Portal list on `portals.scaleflex.com`.

So if a custom domain should always open one Portal, give that domain its own default — setting only the project default is not enough.