> For the complete documentation index, see [llms.txt](https://support.who-umc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.who-umc.org/vigiflow/organisation-administration/creating-suborganisations.md).

# Creating suborganisations

Suborganisations can be set up by administrators.

{% hint style="info" %}
Before starting to set up suborganisations, please refer to the **VigiFlow Intermediate Course**: “**Different ways of receiving ICSRs**” section → “**Suborganisations**” and/or [reach out to UMC](mailto:support@who-umc.org) for dedicated support.
{% endhint %}

When you have considered the practical implications of setting up new sub-accounts you need to create them in the “**`Manage account`**” tab.

### Add the new suborganisation in the right place&#x20;

Suborganisations can be set up hierarchically. &#x20;

<figure><img src="https://844234868-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD7MbxF2Gm1Bf1uqE3mOA%2Fuploads%2FouN8kNzQ8eUejUjJyowr%2F3-1%20two%20pluses.png?alt=media&amp;token=7b1b3ca1-52d3-4b11-ae29-5d210e8b2571" alt="VigiFlow organisation hierarchy with plus signs under the national PV centre and Region A."><figcaption></figcaption></figure>

<figure><img src="https://844234868-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD7MbxF2Gm1Bf1uqE3mOA%2Fuploads%2Fsz5CBlzPCqeoh9ByurDF%2FNew%20organisation%20plus%20sign.png?alt=media&amp;token=6a1b36be-7fcc-4d66-87cf-c84266ebe4e6" alt=""><figcaption></figcaption></figure>

Consider the example above. If you click the sign marked "1", you will create a new suborganisation under Copper District. Such organisation would be able to delegate their reports to *Copperbelt Province*, *National EPI* or *UMC PV centre*.

If the new organisation is created using the plus sign next to “2”, the centre will be placed beneath Steel District. If it is created using the plus sign next to “3”, it will be placed directly beneath *Copperbelt Province*.\
To create a new sub-organisation beneath *National EPI* or the *UMC PV Centre*, scroll down to locate the appropriate plus sign.

Once an organisation has been created, it cannot be moved within the hierarchy. If an organisation is added in the wrong location, it must be removed and then created again in the correct place.

**Once created, an organisation cannot be moved within the hierarchy.** If added to the wrong place, simply remove it and add it to the correct location.&#x20;

### Name the new suborganisation &#x20;

The new organisation is now created. You need to name it with its proper name. This name can be in the local language and should be understandable to any VigiFlow user in your country. For example, “Regional centre” is not a good name; instead, it should be called by the specific name of the regional centre. &#x20;

Click **`Save`**.&#x20;

### Add users&#x20;

Now that the new suborganisation is created, it will automatically appear in “Administrative statistics”, and it is possible to delegate reports to it. &#x20;

However, you must add users to the suborganisation. See:  <a href="/vigiflow/organisation-administration/creating-new-user-accounts.md" class="button primary" data-icon="user">Creating new user accounts</a>


---

# 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://support.who-umc.org/vigiflow/organisation-administration/creating-suborganisations.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.
