> 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/managing-your-team.md).

# Managing your team

How supplier admins invite colleagues, manage access and review their team

Everyone can see who is on the team under **Team**. Only admins can invite people and change their access.

## Roles

| Role       | Can                                                         |
| ---------- | ----------------------------------------------------------- |
| **Admin**  | Do everything an editor can, and manage the team            |
| **Editor** | Edit and submit product data, and write in feedback threads |
| **Viewer** | Read products and feedback, without changing anything       |

Your team always needs at least one admin. To hand over the role, make someone else an admin first.

## Inviting a colleague

1. Open **Team** and click **Invite team member**.
2. Enter their **Email address** and **Name**, and choose a **Role**.
3. Click **Send invite**.

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

They receive an email with a link to set their password. The link expires after 2 days. If it expires, choose **Resend invite** from the menu on their row.

## Changing access

Use the **Role** column to change someone's role. The menu on each row lets you:

* **Reset MFA** if they have lost their phone or authenticator app. They set up two-step verification again at their next sign-in.
* **Sign out everywhere** to end all their sessions, for example if a device is lost.
* **Remove member** when they should no longer have access.

## Reviewing your team

Your customer may ask you to confirm, at a regular interval, that everyone on your team still needs access. When a review is due, you see a reminder after signing in, on the dashboard and on the **Team** page. Admins also get an email.

1. Click **Review team list**.
2. For each person, choose **Keep** or **Remove**. Their recent activity in the portal is shown to help you decide.
3. Click **Confirm review**.

People you remove can no longer sign in, but their name stays on their past work. If they come back, invite them again with the same email address.

Nobody loses access because a review is late.


---

# 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/managing-your-team.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.
