> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/sub-administrations/requirements-for-sub-administrations.md).

# Requirements for Sub-administrations

Check these points before you start with **Sub-administrations**.

This helps you set up the feature without delays.

### What you need first

* Sub-administrations is active
* you can open the main administration
* you have access to manage administrations
* another sub-administration is available to create

### Good to know

* each sub-administration keeps its own daily data
* each one can have its own users and settings
* Sub-administrations are managed from the main administration

### Quick check

1. Open the **License Manager**.
2. Check that **Sub-administrations** is active.
3. Go to **Settings → Administrations**.
4. Check that you can open the page.
5. Check that **Create administration** is available when needed.

### Frequently asked questions

<details>

<summary>Do I need to be in the main administration?</summary>

Yes.

Manage Sub-administrations from the main administration.

</details>

<details>

<summary>Can each sub-administration have its own settings?</summary>

Yes.

That is one of the main reasons to use them.

</details>

<details>

<summary>Can each sub-administration have its own customers and work orders?</summary>

Yes.

Each administration keeps its own daily data.

</details>

### Related topics

* [**Sub-administrations**](/marketplace-packages-and-power-ups/power-ups/sub-administrations.md)
* [**Introduction to Sub-administrations**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/introduction-to-sub-administrations.md)
* [**Manage Sub-administration capacity**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/manage-sub-administration-capacity.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/sub-administrations/requirements-for-sub-administrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.