# Child Organizations
The Child Organizations page lets you create logical boundaries within DataDefender to isolate data between different clients, business units, or environments. This is typically used by managed service providers (MSPs) or enterprises that want to separate visibility between teams.
***
### Creating a Child Organization
Click **Create Child Organization** to go to the creation form.
Fill in the organization name and configure the administrative email address, then save.
***
### Editing a Child Organization
Click the **Edit** button on any row to modify the name or primary contact email.
***
### Deleting a Child Organization
Click the **Delete** button on a row to remove a child organization.
You will be asked to confirm the deletion. **Important:** Deleting a child organization removes access for all users assigned to it. The underlying AWS accounts and their data are not deleted, but users will lose their scoped access.
***
### How Child Organizations Work
* Each child organization has its own set of linked AWS accounts and users.
* Users assigned to a child organization only see data from the accounts within that organization.
* Admin users at the parent organization level can see across all child organizations.
* AWS accounts can only belong to one child organization at a time.
***
### Related Pages
* [Linked Accounts](/portal-overview/settings/linked-accounts.md): AWS accounts must be linked before they can be assigned to a child organization
* [Users](/portal-overview/settings/users.md): Create users and then assign them to child organizations
---
# Agent Instructions: 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:
```
GET https://help.datadefender.io/portal-overview/settings/child-organizations.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.