> 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/supplier-portal-guide/getting-access.md).

# Getting access

How to set your password, sign in, and use two-step verification

## Accepting your invite

You get access to the portal when your customer, or an admin on your own team, invites you. The invite is an email with the subject "You have been invited to" followed by the portal's name.

1. Click **Set your password** in the email.
2. Enter a password of at least 12 characters in **New password** and **Confirm password**. A password manager can generate one for you.
3. Click **Set password**. You are taken to the sign-in page.

{% hint style="warning" %}
The invite link expires after 2 days. If it has expired, ask the person who invited you to send a new one.
{% endhint %}

## Signing in

1. Open the portal and make sure **I'm a supplier** is selected.
2. Enter your **Email** and **Password**, and click **Sign in**.

![The portal sign-in page](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2FvD3JINIJtxFiBLAIv2e0%2Fdop-sign-in.png?alt=media)

Keep the link to the portal from your invite email, or bookmark the sign-in page, so you can find it again.

## Two-step verification

Your customer may require two-step verification. You are then asked for a six-digit code after your password.

The first time, choose how you want to receive codes, if your customer allows more than one method:

* **Email me a code** sends a code to your sign-in email address. The code is valid for 10 minutes.
* **Use an authenticator app** lets an app on your phone, such as Microsoft Authenticator or Google Authenticator, generate the code. Scan the QR code shown with the app, then enter the code it shows.

Tick **Remember this browser** to skip the code on this browser for a number of days. Do not tick it on a shared computer.

If you enter a wrong code too many times, that method is paused for 10 minutes. You can wait, or switch to another method if you have one. If you lose access to your authenticator app, ask an admin on your team to reset your two-step verification.

## Forgotten password

1. On the sign-in page, click **Forgot password?**.
2. Enter your email and click **Send reset link**.
3. Click **Choose a new password** in the email you receive, and choose a new password.

The reset link expires after 2 hours. Check your spam folder if the email does not arrive.

## Changing your name or password

Click your name in the top-right corner and choose **Account settings**. Here you can change your name and password, and manage your two-step verification methods. Changing your password signs you out of every other browser.

## Signing out

Click your name in the top-right corner and choose **Sign out**.

For your security, you are signed out automatically after 24 hours without activity.


---

# 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/supplier-portal-guide/getting-access.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.
