> 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/finding-your-work.md).

# Finding your work

How to find the products you work on, and what statuses and completeness mean

## The dashboard

The dashboard is the first thing you see after signing in. It shows:

* How many items you have been assigned, how many need your attention, and how many changes you have not submitted yet
* **Waiting on you**: what to do next, such as changes to submit, required fields to fill in, or comments to answer
* Your areas, with how complete the products, variant groups and variants in each area are
* The latest comments from your customer

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

## Areas

Your customer groups the products you work on into areas, listed under **Your areas** in the menu on the left. Click an area to see its products.

If an area has variant groups or variants as well, switch between them with the tabs above the list.

![The products in an area](https://2141378775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUonpFWM7AJ0xVVXV1tr%2Fuploads%2Ff5kvMjUxOMUO9diAS6li%2Fdop-area-list.png?alt=media)

### Finding a product

* Click **Needs attention** to see only items with an open question, or **Open changes** to see items with changes you have not submitted.
* Type in the filter box under a column heading to filter on that column. Click a column heading to sort by it.
* Click **Columns** to choose which columns are shown and in what order. **Reset to default** brings back the columns your customer chose.

Click a row to open it.

## Statuses

| Status              | Meaning                                                         |
| ------------------- | --------------------------------------------------------------- |
| **Not started**     | Nothing is filled in yet.                                       |
| **In progress**     | Some fields are filled in, but required ones are still missing. |
| **Complete**        | Every field your customer marked as required has a value.       |
| **Needs attention** | There is an open comment about this item.                       |

## Completeness

The completeness percentage shows how much of what your customer asked for is filled in.

Every field you are asked for counts once for each language and segment you were given. The category counts too, when your customer asks you to choose one. The percentage is rounded down, so it only reaches 100% when everything is filled in.

## Languages and segments

If you work in more than one language, choose the language in the top bar. Do the same for segments, such as markets or channels, if your customer uses them. Your choice applies to every page until you change it.

Languages and segments marked **Read only** can be viewed but not changed.


---

# 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/finding-your-work.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.
