> 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/portal-settings/access.md).

# Access and security

Decide who can open a Portal, and on what terms.

A Portal can be open to anyone with the link, or closed to everyone but the people you approve. This is where you choose, on the **Security** page.

It holds five cards:

| Card                             | Decides                                                      |
| -------------------------------- | ------------------------------------------------------------ |
| **Access management**            | Who can open the Portal, and when.                           |
| **Gallery link security**        | Whether gallery links can be tampered with.                  |
| **Privacy**                      | What may be shared with third-party services.                |
| **Search engines & AI crawlers** | Whether search engines and AI crawlers may index the Portal. |
| **Age verification**             | Whether visitors must confirm their age first.               |

## Access management

*Add an additional level of security to your Portal.*

### Access

The first choice, and it decides what the rest of the card offers.

**Public** means anyone with the link can open the Portal without signing in. Good for press rooms and brand guidelines — anything you'd be happy to see forwarded.

**Private** means visitors must identify themselves. You then decide how they get in: people from your organisation, people you invite, or people who register and are approved.

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FukVnSE8VolmABwle7ZTp%2Fimage.png?alt=media&#x26;token=153e3d7d-7807-49c8-9b79-7ed9040f50bd" alt=""><figcaption><p>The <strong>Access management</strong> card, where a Portal is set public or private.</p></figcaption></figure>

### On a public Portal

One setting appears:

| Setting              | What it does                                                                                             |
| -------------------- | -------------------------------------------------------------------------------------------------------- |
| **Require password** | Adds a shared password phrase everyone uses. Tick it and a field appears — *Enter your password phrase*. |

A shared password and individual accounts solve different problems. A password is quick and anonymous — you can't tell who used it, or withdraw access from one person. Accounts tell you who came, and can be revoked individually.

### On a private Portal

The password disappears and three things take its place:

| Setting                                                     | What it does                                                                              |
| ----------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| **Allow Hub users and administrators to access the portal** | Lets your own DAM users in without a separate Portal account.                             |
| **Self registration**                                       | Lets visitors request an account themselves, rather than being invited.                   |
| **Require approval**                                        | Holds each registration until someone approves it. Only once **Self registration** is on. |
| **Approvers**                                               | Who receives those requests.                                                              |
| **Notification channel**                                    | Where the approval requests are sent.                                                     |

**Self registration** without **Require approval** means anyone who finds the link gets in. That's often fine, and occasionally a surprise — worth deciding rather than defaulting.

### Start and expiry dates

**Start date** and **Expire at** sit at the bottom of the card, and apply whether the Portal is public or private.

Useful for anything with a date attached: a campaign that mustn't go live early, a press embargo, a partner Portal that should close at the end of a contract. Set the expiry when you create the Portal, not when you remember.

### Owner

**Owner** names who owns the Portal; **Change owner** hands it to someone else.

## Gallery link security

*Protect gallery redirect links from URL tampering.*

**Enable gallery link security** signs the links that lead into a gallery, so the folder, filters and metadata they carry cannot be edited by hand. It is **on by default**.

With it on, a link whose parameters have been changed does not show a different set of assets, and does not show an error either: the visitor lands on the Portal's home page. A link you built keeps the context you gave it.

This matters most where a link is the access control — a partner sent to one brand's folder, a journalist to one campaign. Without the signature, editing the folder name in the address bar is enough to see the rest.

{% hint style="info" %}
Filters that arrive through a signed link are applied and locked, so the recipient keeps the view you sent them. See [Filters](https://docs.scaleflex.com/portals/building-a-portal/sections/gallery/gallery-settings/filters.md) for how a locked value looks in the panel.
{% endhint %}

## Privacy

*Configure what data can be shared with external tools.*

**Allow usage of external tools** controls what may be sent to third-party services. It's what enables previews of PowerPoint and Excel files — with it off, those are download-only.

## Search engines & AI crawlers

*Choose whether search engines and AI crawlers may index this portal.*

<figure><img src="https://2536208400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqsq2dR7Fjagf5eTifWZx%2Fuploads%2FkuNTcWfs2QJ79pPJbQ0q%2Fimage.png?alt=media&amp;token=a8bfa00a-e289-4467-9956-62ab2984e2eb" alt=""><figcaption></figcaption></figure>

**Allow search engines and AI crawlers to index this portal** is on by default. Turn it off for a Portal you don't want turning up in search results or in AI assistants' answers — an internal brand hub, a partner Portal, a campaign that isn't public yet.

With it off, the Portal's pages ask crawlers not to index them or follow their links, and the Portal is removed from its sitemap. This covers every address the Portal is published at, including a custom domain and shared links.

### What a crawler is offered

With it on, the Portal publishes two files beside its pages:

| File              | For                                                                            |
| ----------------- | ------------------------------------------------------------------------------ |
| **`sitemap.xml`** | Search engines, in the usual way.                                              |
| **`llms.txt`**    | AI assistants — a plain list of the Portal's pages, with their names and URLs. |

`llms.txt` exists because an AI assistant reading a Portal built of sections has a hard time working out what the pages are. Handing it a list means the assistant describes your Portal from its real structure rather than guessing.

### What never reaches either file

Both are built by reading the Portal **as an anonymous visitor** — which is what a crawler is. Anything that visitor cannot reach is simply not there to list:

* A Portal that is **private**, **password-protected** or **age-gated**, because the anonymous read is refused.
* A Portal that is **unpublished**, **redirected**, or has indexing turned off.
* A page that is **archived**, **restricted to an audience**, or still a **draft**.
* **Form and system pages**, and dataset entry pages, which need a row to mean anything.
* Any page reachable **only** from one of the above — a restricted page's own links are not followed, so the names of pages behind it stay unpublished too.

Pages are found the way a visitor finds them: from the home page, following links. A page nothing links to will not be listed even if it is public.

{% hint style="warning" %}
This is a request, not a lock. Well-behaved crawlers respect it, but anyone with the link can still open the Portal. To restrict who gets in, set **Access** to **Private** or use **Require password** in **Access management** above.
{% endhint %}

## Age verification

**Enable age verification page** puts a gate in front of the Portal: visitors give their date of birth before they see anything. It's the drinks-industry requirement, and anything else with a legal age attached.

| Setting                     | What it does                                                           |
| --------------------------- | ---------------------------------------------------------------------- |
| **Minimum age**             | The age a visitor has to reach to get in. **18** unless you change it. |
| **Redirect URL on decline** | Where to send visitors who fail age verification.                      |

Turning it on adds an **Age verification** page to the Portal, which you can then style like any other system page.

A visitor who passes is remembered for **30 days**, so regular visitors are not asked on every visit. After that the gate returns.

{% hint style="warning" %}
Age verification only applies to a **public** Portal. Switching **Access** to **Private** turns it off — a Portal that already asks visitors to sign in has no anonymous arrival to gate.
{% endhint %}

## Saving

Changes here raise the **Save** bar at the top of the page; nothing takes effect until you use it. **Cancel** puts the form back as it was.

## Related

* [Authentication](https://docs.scaleflex.com/portals/portal-settings/authentication.md): signing in with a Google account.
* [Users](https://docs.scaleflex.com/portals/portal-settings/users.md): the people who have access.
* [Terms & Conditions](https://docs.scaleflex.com/portals/building-a-portal/pages/system-pages/registration/terms-and-conditions.md): requiring acceptance at registration.
