> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-the-data-onboarding-portal/how-to-brand-and-secure-the-portal.md).

# How to brand and secure the portal

A guide to giving the portal your brand and choosing how suppliers sign in

Suppliers should feel they are working with you, not with a third-party tool. Branding gives the portal your name, logo, colours and typeface, and the portal settings decide how suppliers sign in and how often their admins check their team.

Both are found under **Settings > Data onboarding**, in **Branding** and **Portal settings**.

## How to brand the portal

Open **Settings > Data onboarding > Branding**. The settings are on the left, and a live preview of the portal on the right shows your changes as you make them.

![Portal branding with live preview](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FsLzfN5QimS1wvzx9BBSp%2Fdop-branding.png?alt=media)

1. Pick one of the **Brand presets** as a starting point, or skip straight to the fields below.
2. Enter a **Portal name**. Suppliers see it in the portal header, the browser tab, and every email the portal sends them. If you leave it empty, your Struct PIM name is used.
3. Choose a **Logo**. Click **Upload…** to use your own (PNG, JPG, WebP or SVG, up to 5 MB), or choose **Monogram** to show the first letter of the portal name. The logo is also used as the browser tab icon.
4. Choose a **Brand colour** for the portal header and key surfaces, and an **Accent colour** for buttons, links, progress and the active tab. Pick a swatch or click **Custom colour** to enter your own.
5. Choose a **Typeface** for all text in the portal. Click **Browse all typefaces** for the full list.
6. Click **Save**.

{% hint style="info" %}
The portal also uses the portal name when it talks about you, for example "Delivering data to Nordlys Home". Use your company name, not a name like "Nordlys Home Supplier Portal".
{% endhint %}

{% hint style="warning" %}
If a colour is hard to read against both white and dark text, the preview warns you. Choose a darker or lighter shade so suppliers can read buttons and the header.
{% endhint %}

## How to find the portal address

Your suppliers sign in to the portal at its own web address. Suppliers get the link in their invite email, but you can also share it yourself.

Open **Settings > Data onboarding > Portal settings**. Under **Portal address**, click the copy icon next to **Supplier portal URL** to copy the link, or **Open portal** to see the portal yourself. You can also open the portal with **Open portal** at the top of the data supplier list.

![Portal settings](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FwjX2ZTT0dPxpSOeqzkmx%2Fdop-portal-settings-v2.png?alt=media)

## How to choose how suppliers sign in

Open **Settings > Data onboarding > Portal settings**. The **Sign-in security** section decides how supplier users prove who they are.

* Turn on **Require two-step verification for all supplier users** to ask for a code after the password. Supplier users who have not set it up are signed out, and set it up at their next sign-in.
* Under **Allowed methods**, choose **Email code**, **Authenticator app (TOTP)** or both. Email codes are convenient, but an authenticator app is the stronger choice where security matters.
* **Remember a browser for** decides how many days a supplier can skip the code on a browser they trust. Enter 0 to turn this off. The maximum is 90 days.

Click **Save** to apply the changes.

{% hint style="info" %}
Removing a method does not sign out users who already verified with it. Use **Sign everyone out** on the supplier's **Invited users** tab if you need that.
{% endhint %}

## How to ask suppliers to review their team

People change jobs, and a supplier's user list can go out of date. A team review asks each supplier's admins to confirm, at a regular interval, that everyone on their list should still have access.

1. In **Portal settings**, turn on **Ask supplier admins to review their team list regularly**.
2. Set **Review every** to the number of days between reviews. The suggested interval is 90 days, and the minimum is 14.
3. Choose when the **First review** is due: for everyone now, or one interval after each supplier was created.
4. Click **Save**.

Supplier admins get an email 14 days before a review is due, and again if it is overdue. Nobody loses access because a review is late. You can follow each supplier's reviews on its **Team review** tab.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.struct.com/tutorials/guides/how-to-use-the-data-onboarding-portal/how-to-brand-and-secure-the-portal.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
