> 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/msp/getting-started/opening-an-msp-space.md).

# Opening an MSP space

You receive a link by email to sign in to the platform created for you.

As soon as you sign in, you can add information about your company. This information is used for billing.

You then have access to the platform, organized as follows:

1. **Accounts:** this tab lets you add accounts and manage license purchases for each account
2. **Sales support:** all the information we provide to help you understand Stoïk products
3. **Overview:** this tab gives you an overview of license consumption by tool
4. Your **Invoices**

**Settings** then give you access to:

1. Your company **information**, to complete on your first sign-in
2. **Access and notifications:** you can add one or more users to the MSP platform. For now, there is no differentiated access between users.

Your personal settings (profile and security) are in **User settings**, in the menu in the lower-left corner of the app.


---

# 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/msp/getting-started/opening-an-msp-space.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.