> For the complete documentation index, see [llms.txt](https://docs.artific.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.artific.nl/en/for-administrators/organization/child-organizations.md).

# Child organizations

Managing organisations beneath your own. Found under **Organization management → Child organizations**.

This screen is only available to partner organisations. If it is not in your menu, your organisation does not manage others.

## What a child organisation is

A separate organisation created under yours, with its own users, assistants, knowledge and branding. Used by partners managing several clients, and by larger organisations separating divisions that should not see each other's material.

The parent can create children, join them, switch into them, copy assistants into them, control which reports they see, and delete them. Some things (user group membership and shared connectors) can cascade downwards.

## The list

| Column              | What it shows                                                      |
| ------------------- | ------------------------------------------------------------------ |
| **Name**            | The organisation, with its icon. Partner organisations are marked. |
| **Your membership** | Whether you are a member of it.                                    |
| **Primary color**   | Its brand colour.                                                  |
| **Reports**         | Whether Activity and Tokens reporting are enabled for it.          |
| **Session logs**    | Whether its administrators can see conversation logs.              |

## Actions

| Action                                   | What it does                                                           |
| ---------------------------------------- | ---------------------------------------------------------------------- |
| **Switch to this organization**          | Work inside that organisation. You may be asked to sign in again.      |
| **Become a member of this organization** | Join it, so you can switch into it.                                    |
| **Copy assistants**                      | Copy one of your assistants into it.                                   |
| **Enable / disable usage reports**       | Controls whether that organisation sees its **Activity** report.       |
| **Enable / disable token reports**       | Controls whether it sees its **Tokens** report.                        |
| **Show / hide session logs**             | Controls whether its administrators can read conversation transcripts. |
| **Leave this organization**              | Give up your membership.                                               |
| **Delete this organization**             | Remove it entirely.                                                    |

{% hint style="danger" %}
Deleting a child organisation removes everything in it: users, assistants, knowledge, history. There is no undo.
{% endhint %}

The session logs switch deserves thought. Transcripts contain whatever users typed. Hide them where the child organisation's administrators should not read their colleagues' conversations.

## Creating one

**Create child organization** opens the same form as [Organization settings](/en/for-administrators/organization/settings.md): name, default user groups, self-signup allowlist, login methods, data retention and the advanced options. Everything can be changed afterwards.

## Copying an assistant

**Copy assistants** duplicates one of your assistants into a child organisation.

| Field                   | What to choose              |
| ----------------------- | --------------------------- |
| **Assistant to copy**   | The assistant to duplicate. |
| **Target organization** | Where it goes.              |

The copy appears in the target organisation's assistant list, where its administrators can adapt it.

{% hint style="info" %}
The copy is independent. Later changes to your original do not flow to it, and the target organisation's changes do not flow back. For genuinely shared material, use [shared connectors](/en/for-administrators/organization/shared-connectors.md) or the [Toolbox library](/en/for-administrators/toolbox/library.md), which stay linked.
{% endhint %}

Check afterwards that the copied assistant has what it needs on the other side: knowledge collections, tools and user groups do not travel with it.

## A workable pattern

For a partner managing several clients:

1. Build a reference assistant in your own organisation and get it right.
2. Copy it into each client organisation.
3. Adapt each copy to that client's knowledge and branding.
4. Share connectors from the parent so integrations are configured once.
5. Publish common Toolbox elements through the [library](/en/for-administrators/toolbox/library.md), so improvements reach everyone.