> 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.md).

# Sub-administrations

Manage multiple administrations from one environment with clearer separation and control.

**Sub-administrations** help you manage multiple administrations in one OutSmart environment.

Use them when you want separate daily data with one central starting point.

{% hint style="info" %}
Sub-administrations is available as a **Power-Up**.
{% endhint %}

### In this guide

* [**Introduction to Sub-administrations**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/introduction-to-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)
* [**Create a sub-administration**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/create-a-sub-administration.md)
* [**Switch between administrations**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/switch-between-administrations.md)
* [**Delete a sub-administration**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/delete-a-sub-administration.md)
* [**Sync settings to sub-administrations**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/sync-settings-to-sub-administrations.md)
* [**What you can sync to sub-administrations**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/what-you-can-sync-to-sub-administrations.md)
* [**Use sub-administrations in the mobile app**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/use-sub-administrations-in-the-mobile-app.md)
* [**Manage permissions for Sub-administrations**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/manage-permissions-for-sub-administrations.md)
* [**Add employees to a sub-administration**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/add-employees-to-a-sub-administration.md)
* [**Manage Sub-administration capacity**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/manage-sub-administration-capacity.md)
* [**Requirements for Sub-administrations**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/requirements-for-sub-administrations.md)

### What you do with Sub-administrations

* keep customers, work orders, invoices, and settings separate
* switch between administrations without signing out
* keep shared setup aligned where needed

### Recommended order

1. Start with [**Introduction to Sub-administrations**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/introduction-to-sub-administrations.md).
2. Continue with [**Activate Sub-administrations through the License Manager**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/activate-sub-administrations-through-the-license-manager.md).
3. Check [**Requirements for Sub-administrations**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/requirements-for-sub-administrations.md).
4. Then [**create a sub-administration**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/create-a-sub-administration.md).
5. Use [**Switch between administrations**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/switch-between-administrations.md) for daily work.
6. Use sync, permissions, mobile access, and capacity management when needed.

### Related topics

* [**Power-Ups**](/marketplace-packages-and-power-ups/power-ups.md)
* [**OutSmart Marketplace**](/marketplace-packages-and-power-ups/marketplace.md)
* [**Manage your Power-Ups**](/marketplace-packages-and-power-ups/marketplace/manage-your-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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/sub-administrations.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.