> 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/account-management/adding-an-account.md).
# Adding an account
As an MSP, you need the client's consent before you can manage their cyber tools. Connecting to the client's Stoïk Protect space is therefore a critical step in the process. This step also grants you exclusivity on the client's account.
To add an account:
{% stepper %}
{% step %}
### Create the account
In the `Accounts` tab, click `New account`.
{% endstep %}
{% step %}
### Account information
Add the required information: you can enter the company name or its business identification number.
{% endstep %}
{% step %}
### Select the company
Select the company, then complete the domain name and account email address.
{% endstep %}
{% step %}
### Connection request
Request connection to a Stoïk Protect space. Once the account is created, this step is required before you can buy licenses. Enter your client's email address.
{% hint style="warning" %}
If your client is already insured with Stoïk, you **must** enter **the email address already used in their space** to sync the correct Stoïk Protect space.
{% endhint %}
{% endstep %}
{% endstepper %}
The link in the email sent to the client is valid for **7 days.** After that, the link expires and you must resend the connection request.
{% hint style="success" %}
Once the connection is active, you can access your client's Stoïk Protect space via the resend link.
{% endhint %}
---
# 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/account-management/adding-an-account.md?ask=&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.
