> 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/what-you-can-sync-to-sub-administrations.md).

# What you can sync to sub-administrations

When you sync to sub-administrations, you choose which setup items to copy.

This lets you keep the right parts consistent.

### Common items you can sync

You can usually sync items such as:

* forms
* workflows
* work types and statuses
* custom fields
* templates
* dashboards and reports
* invoice and quotation settings
* email and PDF settings

### When to sync these items

Sync these items when you want:

* the same setup in each administration
* a faster rollout for new administrations
* fewer manual changes afterward

### Good practice

Sync related items together.

For example, keep workflows, work types, and forms aligned.

### Frequently asked questions

<details>

<summary>Do I need to sync everything at once?</summary>

No.

You can sync only the items you need.

</details>

<details>

<summary>Should I sync related settings together?</summary>

Yes.

That helps keep the setup consistent.

</details>

<details>

<summary>Can I leave some items different per administration?</summary>

Yes.

Only sync the parts you want to standardize.

</details>

### Related topics

* [**Sub-administrations**](/marketplace-packages-and-power-ups/power-ups/sub-administrations.md)
* [**Sync settings to sub-administrations**](/marketplace-packages-and-power-ups/power-ups/sub-administrations/sync-settings-to-sub-administrations.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/what-you-can-sync-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.