> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/global-settings/groups-users-and-permissions/sub-organizations/how-to-create-a-sub-organization.md).

# How to create a Sub-Organization

## Create a new Sub-Organisaztion:

<div data-full-width="false"><figure><img src="/files/4cxHmVa98opGc9TCbwwZ" alt="Sub-Organizations List Overview"><figcaption></figcaption></figure></div>

Click on the `+ NEW` button

<figure><img src="/files/qPMaLkbxARMJIJz3dptz" alt="Sub-Organization New Button" width="97"><figcaption></figcaption></figure>

The following menu will be displayed:

<figure><img src="/files/xeO9IwKC9KXW1wmsKcxx" alt="Create Sub-Organization Form" width="375"><figcaption></figcaption></figure>

Enter the details of the sub-organization you want to create, the name and description, then click on the `SAVE` button. You should then find your newly created sub-organization at the bottom of the list of existing sub-organizations.

## Editing sub organizations

<figure><img src="/files/NY09lr73BlDKmspCKgWH" alt="Edit Sub-Organization Icon" width="161"><figcaption></figcaption></figure>

**Manage Users:**

<figure><img src="/files/ddg9YCknjc09fv3zqcQK" alt="Manage Users in Sub-Organization" width="375"><figcaption></figcaption></figure>

* **Adding Users:** Administrators can create new user accounts and assign them to the appropriate sub-organization.
* **Assigning Roles and Permissions:** Administrators can set the roles and permissions for users within a suborganization. This typically involves assigning access rights to specific documents, folders or functions in the document management system.
* **Manage profile details:** Administrators can edit profile details of users within the sub-organization, such as: B. Contact information or department affiliation. This allows for updated and accurate management of user data.

<figure><img src="/files/fdb4CjBNEbLNy8LcHdDp" alt="Add User to Sub-Organization Modal" width="375"><figcaption></figcaption></figure>

You can add a new user to the organization and have the option of whether to remove the user from other groups.

**Edit User:**

<figure><img src="/files/cxNRYAo9KKdKZ5M8OCfE" alt="Edit User in Sub-Organization" width="375"><figcaption></figcaption></figure>

* **Editing suborganization settings:** Administrators can edit the settings and properties of a suborganization, including its name, description, or hierarchy level within the system.
* **Edit user details:** Administrators can edit the details of individual users within a sub-organization, for example to adjust their access rights or update their contact information.

**Delete User:**

* **Deleting sub-organizations:** Administrators may also have the ability to delete sub-organizations if they are no longer needed or if a restructuring of the organizational structure is required. When deleting a suborganization, administrators must ensure that all users and data associated with it are handled properly.

These management features enable administrators to effectively manage and adapt the user accounts and organizational structures within a document management system to meet the company's changing needs and processes.


---

# 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://docs.docbits.com/administration-and-setup/settings/global-settings/groups-users-and-permissions/sub-organizations/how-to-create-a-sub-organization.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.
