> 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/creating-a-portal.md).

# Creating a Portal

Start a new Portal — from nothing, or from a template.

From the Portals list, select **+ Add portal**.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FOBYk599PdjHuyo20QkaB%2FGemini_Generated_Image_f3ww7nf3ww7nf3ww.jpeg?alt=media&#x26;token=3a730fd9-6593-4c6f-baba-a65dbc1b1f70" alt=""><figcaption><p><strong>+ Add portal</strong>, top right of the Portals list.</p></figcaption></figure>

## Choose a starting point

|                        |                                                                                                                                             |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| **Start from scratch** | An empty Portal with the system pages already in place. Best when you know what you want.                                                   |
| **Templates**          | A ready-made Portal you then change — a brand hub, a press room, a product catalogue. Fastest way to see what a finished Portal looks like. |

A template is a starting point, not a commitment: everything in it can be changed or removed.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2Fm1oNTPzCG5yXvVmnhjw6%2Fimage.png?alt=media&#x26;token=06e86621-8769-4305-80e6-16f54ec666c9" alt=""><figcaption><p>Choosing a starting point — an empty Portal, or one of the templates.</p></figcaption></figure>

## Set it up

Whichever you pick, a short setup follows. None of it is permanent — every one of these can be changed later from the builder or from **Settings**.

| Step              | What you set                                                             |
| ----------------- | ------------------------------------------------------------------------ |
| **Basic info**    | The Portal's name, its slug, and the primary language.                   |
| **Colors**        | Your primary colour, and whether buttons and links use a different one.  |
| **Typography**    | The typefaces for headings and body text.                                |
| **Layout**        | How pages are arranged — top navigation or a sidebar.                    |
| **Access pages**  | The look of the sign-in, registration and other system pages.            |
| **Quick presets** | A complete look applied in one go, if you'd rather not choose each part. |

{% hint style="info" %}
The **slug** is the Portal's address, so it is the one worth a moment's thought. Everything else is cosmetic and easily changed.
{% endhint %}

All of it can be revisited later under [Portal settings → General](/portals/portal-settings/general.md).

## What you get

A new Portal arrives as a **draft**, with its system pages already created — sign in, register, request access, forgot password and the rest. Nothing is visible to anyone until you publish it.

From here: add pages and sections in the builder, decide who can get in, then publish.