> 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/get-started.md).

# Get started

MSI organizes everything around the medical device you're working on. This page explains how organizations, workspaces and devices fit together, how to switch between them, and where to find each part of the product.

## How MSI is organized

MSI uses three levels:

| Level            | What it is                                                                                                                  | Example              |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------- | -------------------- |
| **Organization** | Your company's account. Each organization has its own workspaces and devices.                                               | Acme Medical         |
| **Workspace**    | A group of related devices, such as a product line or business unit. Switching workspaces shows a different set of devices. | Cardiac Monitoring   |
| **Device**       | One medical device. Threat models, readiness checks, documents and other results all belong to a device.                    | Acme Cardiac Monitor |

Most pages show results for one device at a time, so selecting the right device is usually the first thing you do.

## Switch organization, workspace or device

The breadcrumb at the top of each page shows where you are: organization, then workspace, then device.

* **Switch organization:** Select the organization name in the breadcrumb, then choose from the **Organizations** list. Pending invitations to other organizations also appear here.
* **Switch workspace:** Select the workspace name in the breadcrumb, then choose from the **Workspaces** list. If you're an organization admin, the breadcrumb reads **All Workspaces**.
* **Switch device:** Select the device name in the breadcrumb, then choose from the **Devices** list.

You can also switch devices from the sidebar. The device selector at the top of the sidebar shows the current device (or **Select a device** if none is chosen). Select it to see every device in the current workspace, then select a device to switch to it.

{% hint style="info" %}
If you open a page that needs a device and haven't picked one, MSI asks **Which device are you working on?** and shows your devices. Select one to continue. If your workspace has no devices yet, you'll see options to add one. See [Create your first device](/medcrypt-documentation/msi/get-started/create-your-first-device.md).
{% endhint %}

## Use the sidebar

The sidebar is split into sections. Which items you see depends on what your organization's plan includes.

### Main pages

| Item                 | What it's for                                                                                                                              |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Dashboard**        | An overview of the selected device. See [Understand your dashboard](/medcrypt-documentation/msi/get-started/understand-your-dashboard.md). |
| **My Work**          | Everything assigned to you, across all devices. The badge shows how many open assignments you have.                                        |
| **Device Knowledge** | Everything MSI knows about the device: its profile, architecture, versions and the knowledge built from your documents.                    |
| **Deliverables**     | The documents and packages you're producing for regulators.                                                                                |

### Intelligence

Registers and reference material you'll check regularly, such as the **Risk Register** (your device's living list of threats) and **Regulatory Intel**.

### Activities

The analyses you run on a device, such as **Threat Model**, **Import Report**, **FDA eSTAR Readiness** and **Maturity Assessment**. **Guided Questions** also sits here; its badge shows how many open questions the selected device has. See [Answer guided questions](/medcrypt-documentation/msi/get-started/answer-guided-questions.md).

You can collapse or expand the **Intelligence** and **Activities** sections. MSI remembers your choice in this browser.

### Bottom of the sidebar

* **Documents:** the document collections you've uploaded.
* **Your account menu:** select your profile to open **Settings**, change the theme, open **Help & Support**, view **About**, or **Logout**.
* **Notifications:** the bell icon. See [Check your notifications](#check-your-notifications).
* **Help & Support:** the help icon. See [Get help and take a tour](#get-help-and-take-a-tour).

To give yourself more room, collapse the sidebar with the arrow at the top. Hover over the collapsed device selector to see the current device's name.

## Check your notifications

Select the bell icon at the bottom of the sidebar to open **Notifications**. The badge counts unread notifications plus any invitations waiting for you to accept.

On the Notifications page you can:

* Accept invitations to join other workspaces or organizations.
* Select a notification to go to the item it's about.
* Mark a notification as read or unread, or delete it.

## Get help and take a tour

Select the help icon at the bottom of the sidebar (or **Help & Support** in your account menu) to open these options:

| Option                         | What it does                                                                                            |
| ------------------------------ | ------------------------------------------------------------------------------------------------------- |
| **Contact us**                 | Opens an email to the support team.                                                                     |
| **Report a Bug**               | Opens a form to submit a structured bug report.                                                         |
| **Take a Tour**                | Starts a guided walkthrough of the page you're on.                                                      |
| **How Device Knowledge works** | Explains how MSI turns your documents into device knowledge, including traceability and change history. |
| **About**                      | Shows version and system details.                                                                       |

**Take a Tour** depends on the page you're viewing. On most pages it starts **Navigation Basics**, which walks through the organization, workspace and device selectors. On a report page, such as a maturity assessment, eSTAR readiness check, threat model or the Risk Register, it explains that report section by section. Try it on different screens to learn about each one.

## Ask a question from any page

The **Ask MSI** button in the bottom-right corner of every page opens an assistant that can answer questions about your device or your whole portfolio. See [Ask MSI a question](/medcrypt-documentation/msi/get-started/ask-msi.md).

## Next steps

* [Create your first device](/medcrypt-documentation/msi/get-started/create-your-first-device.md): upload your documents so MSI can build a device profile and start its analyses.
* [Understand your dashboard](/medcrypt-documentation/msi/get-started/understand-your-dashboard.md): learn what each dashboard card shows.
* [Manage users and access](/medcrypt-documentation/msi/assign-work-and-track-my-work/manage-users-and-access.md): invite teammates and understand roles.


---

# 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/get-started.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.