> For the complete documentation index, see [llms.txt](https://www.docpartner.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.docpartner.dev/api/sms-partner/sous-comptes/activation.md).

# Activation

Découvrez comment activer la fonctionnalité création de sous-comptes.

### Demande d'activation de la fonctionnalité sous-comptes

{% hint style="info" %}

#### Comment activer cette fonctionnalité ?

Veuillez contacter [l'équipe technique](https://www.smspartner.fr/contact/).
{% endhint %}

SMS Partner vous donne la possibilité de créer des sous-comptes. Ainsi vous pouvez gérer un nombre illimité de sous-compte à partir de votre compte principal.

### Création des sous-comptes

{% hint style="info" %}
Pour créer des sous-compte à partir de votre compte maitre, il y a trois solutions possibles.
{% endhint %}

* Via notre API : Voir la [page création de sous-comptes](/api/sms-partner/sous-comptes/creation-dun-sous-compte.md)
* Via le fichier Excel : Veuillez télécharger, compléter et nous renvoyer le [fichier modèle](https://my.smspartner.fr/subaccount_model.xls).
* Via la plateforme : Une fois l'option activé vous pouvez en créer [ici](https://my.smspartner.fr/dashboard/sous-compte/liste-sous-compte).


---

# 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://www.docpartner.dev/api/sms-partner/sous-comptes/activation.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.