> For the complete documentation index, see [llms.txt](https://manual.blocworx.com/blocworx-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.blocworx.com/blocworx-documentation/no-code-development/manage-blocworx-instances/parent-and-child-instances.md).

# Parent and Child Instances

If you have a reseller agreement with Blocworx and have met all the requirements to [create your own instances](/blocworx-documentation/no-code-development/manage-blocworx-instances.md), then you can make use of our Parent/Child Instance functionality.

A Child instance is an instance that has the ability to use configurations, modules and roles from another instance,that other instance would be considered a parent. The child instance is like a replica of the parent instance. This means you can build modules once, create various instances for different customers and give them all the same module. This prevents having to rebuild modules, or import modules. It also means that you only have to maintain the one module no matter how many instances are using it.

![](/files/3xQcQfcmFXSMYzLAiUGS)

The configurations that are shared to the child instance from a parent are:

1. [Roles](/blocworx-documentation/admin-and-development/roles-and-permissions/roles.md)
2. [Pages](/blocworx-documentation/page/page-overview.md) (including the entire structure)
3. [Modules](/blocworx-documentation/module/module-overview.md), if you have chosen to[ allow that module to be shared](/blocworx-documentation/module/edit-a-module/make-this-module-available-to-child-instances.md).

Users and Data is not shared, you must set up a user for every child instance. However, [as a super user](/blocworx-documentation/no-code-development/extra-hidden-features.md#super-user), you can access the instance with your existing login.

{% hint style="success" %}
Coming Soon: The ability to pass individual blocs as opposed to entire modules.
{% endhint %}


---

# 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://manual.blocworx.com/blocworx-documentation/no-code-development/manage-blocworx-instances/parent-and-child-instances.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.