> For the complete documentation index, see [llms.txt](https://docs.medcrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.medcrypt.com/medcrypt-documentation/msi/assign-work-and-track-my-work.md).

# Work with your team

When a guided question, threat or control needs someone else's input, assign it to a teammate, or to a Medcrypt expert if your plan includes that service. Each assignment carries its own conversation thread, and **My Work** collects everything assigned to you and everything you've asked others to look at.

## Before you begin

* Select the device the work belongs to.
* Guided questions, threats and controls come from threat modeling, so your organization's plan must include Threat Modeling to assign them.
* The person you assign work to must have access to the device's workspace. See [Manage users and access](/medcrypt-documentation/msi/assign-work-and-track-my-work/manage-users-and-access.md).
* Asking a Medcrypt expert is a paid option. Your organization's plan must include Medcrypt expert services.

## Assign an item to a teammate

You can assign items from the pages where they live: **Guided Questions**, the **Risk Register** (threats and controls), and the matching cards on your dashboard.

1. On the item, select the assignee control. It shows **Unassigned** when nobody owns the item yet.
2. On the **Workspace** tab, under **Who should answer this?**, select a teammate.
3. Under **What do you need?**, describe what you need from them. If the item is based on a quote from your documents, the flyout shows it, and your teammate will see it too.
4. Select **Send**.

Their reply appears on the item and in **My Work**.

To find items to assign, select **My Work** in the sidebar, then **Assign Work**. Choose a page to go to. Each page has assign controls on individual items.

## Reassign an item

1. Select the current assignee's name on the item.
2. Search for and select a different teammate.

To hand the item to Medcrypt instead, select **Need Medcrypt Help?** at the bottom of the list.

## Ask a Medcrypt expert

1. On the item, open the assign flyout and select the **Ask a Medcrypt Expert** tab.
2. Under **What do you need?**, describe your question.
3. Select **Send**.

Your request goes to your organization's designated Medcrypt contact, and their answer arrives in the item's thread. If your contact isn't yet a member of the workspace, MSI shows **Sent to Medcrypt — access being provisioned**, and your organization's admins receive an access request to approve. See [Manage users and access](/medcrypt-documentation/msi/assign-work-and-track-my-work/manage-users-and-access.md#approve-or-decline-an-access-request).

If your plan doesn't include Medcrypt expert services, the tab shows **Medcrypt expert services** with a link to contact sales.

## Track your work in My Work

In the sidebar, select **My Work**. The count beside it shows how many open items you have.

The list shows each assignment's **Item**, **Device**, **Owner** and **Status**. Narrow it with:

* The search box, to find items by device or item name.
* The **Status** filter, to show **Open** or **Done** items.
* **Assigned to me**, to show only items you own and hide requests you made of others.

Each assignment has one of these statuses:

| Status          | Meaning                                                      |
| --------------- | ------------------------------------------------------------ |
| **Open**        | Assigned and waiting for a response.                         |
| **In progress** | The assignee has started on it.                              |
| **Answered**    | The assignee has replied with what they consider the answer. |
| **Done**        | Closed out.                                                  |
| **Cancelled**   | Withdrawn, or the item itself no longer applies.             |

## Discuss an item in its thread

1. In **My Work**, select **Thread** on the assignment. The button shows the message count once there are replies.
2. Read the request and replies. Each reply shows who wrote it and whether they're on **Your team** or from **Medcrypt expert services**.
3. Type in **Write a reply…**. If your reply answers the request, select **This is the answer**.
4. Select **Reply**.

To work on the item itself rather than discuss it, select **Go to item**. MSI opens the page the item lives on.

## Close or reopen an assignment

When the work is finished:

1. In **My Work**, select **Mark done** on the assignment.
2. Optionally add a note, then confirm.

This closes the assignment for everyone on the thread and posts a note to it. An expert can answer a request, but closing it is your team's decision.

To bring a closed assignment back, select **Reopen**. It moves back to the **Open** list.

## Next steps

* [Answer guided questions](/medcrypt-documentation/msi/get-started/answer-guided-questions.md): the questions you're most likely to assign.
* [Triage risks in the Risk Register](/medcrypt-documentation/msi/review-your-threat-model/triage-risks-in-the-risk-register.md): assign threats and controls for review.
* [Manage users and access](/medcrypt-documentation/msi/assign-work-and-track-my-work/manage-users-and-access.md): add the teammates you want to assign work to.


---

# 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.medcrypt.com/medcrypt-documentation/msi/assign-work-and-track-my-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.