> 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/introduction-to-sub-administrations.md).

# Introduction to Sub-administrations

**Sub-administrations** let you manage more than one administration in OutSmart.

Each administration keeps its own daily data.

### What you do with Sub-administrations

* keep customers, work orders, invoices, and settings separate
* manage several administrations from one main environment
* switch between administrations without signing out
* keep shared settings aligned where needed

### When Sub-administrations fits

Use Sub-administrations when you manage:

* multiple companies
* multiple branches
* separate teams or business units

### How it works

You start from one main administration.

From there, you create and manage your sub-administrations.

Each sub-administration can have its own setup and users.

### What stays separate

Each sub-administration has its own:

* customers
* work orders
* invoices and quotations
* settings and users

### Related topics

* [**Sub-administrations**](/marketplace-packages-and-power-ups/power-ups/sub-administrations.md)
* [**Activate Sub-administrations through the License Manager**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/activate-sub-administrations-through-the-license-manager.md)
* [**Power-Ups**](/marketplace-packages-and-power-ups/power-ups.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/introduction-to-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.