> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/onboarding/cockpit.md).

# Cockpit

If you are invited to more than one Stoïk Protect account, a **Cockpit** section appears in the sidebar. It gives you a cross-account view of your accounts, without switching spaces one by one.

Typical users: MSPs managing several clients, group CISOs overseeing subsidiaries, IT providers, or holding admins.

The Cockpit includes two views:

* Deployment: deployment status of each cyber tool, for every account you manage
* Alerts: all alerts from all tools and all accounts, in one table

Users with access to a single Stoïk Protect account do not see Cockpit.

## Access Cockpit

1. Sign in to Stoïk Protect with an account that belongs to two or more Protect spaces.
2. In the left sidebar, open the **Cockpit** section
3. Click the **Deployment** or **Alerts** tab

To work inside one client’s space (configure a tool, resolve an alert in context), open that account from the account switcher at the bottom of the sidebar.

## Deployment

Deployment is a matrix: one row per account, one column per tool (for example External Scan, AD scan, Cloud scan, Simulation, MDR, Email Security...).

Each cell shows where that tool stands for that account.

### Tool statuses

| Status                        | Meaning                                                                                                                                |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Activated**                 | The tool is enabled for this account and is set up and running.                                                                        |
| **Enabled but not activated** | The tool is enabled, but setup is not finished. The client (or you) still needs to complete activation.                                |
| **Not enabled**               | The tool is not enabled for this account.                                                                                              |
| **Not relevant**              | The tool was marked as not applicable for this account (for example already covered elsewhere). This is a valid choice, not a failure. |

### KPIs at the top of the page

Three indicators summarise your fleet:

* **Coverage**: share of possible tool slots that are enabled across all accounts. Use this to see how much of your catalog you deploy.
* **Activation rate**: among enabled tools (excluding Not relevant), how many are activated. Use this to spot tools stuck in setup.
* **Fully protected clients**: share of accounts where every enabled tool is activated. Use this to see how many clients are in a clean state versus needing follow-up.

### Filters and search

Use Tools, Last active, and Added date filters, and the search bar, to narrow the list when you manage many accounts.

## Alerts

The Alerts tab lists alerts from all tools and all accounts you can access in Cockpit.

Each row typically includes the account, the tool, alert details, and an Action column that tells you whether you need to do something.

### Action column

<table><thead><tr><th width="201.0625">Action</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Informational</strong></td><td>No action is required from you. The tool is fully managed by Stoïk SOC.</td></tr><tr><td><strong>Action required</strong></td><td>You or the client should investigate or remediate.</td></tr></tbody></table>

Use this view to prioritise work across your portfolio instead of opening each account separately.

To handle an alert in full context (history, remediation, settings), open the relevant account and go to the tool’s alerts page.


---

# 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.stoik.io/onboarding/cockpit.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.