> For the complete documentation index, see [llms.txt](https://timberid.gitbook.io/timberid/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://timberid.gitbook.io/timberid/user-guide/administration-guide/creating-organizations.md).
# Creating Organizations
TimberID Organizations are boundaries of data visibility. No data between organizations is shared nor is data from an organization shared publicly.
If an organization wishes to share data with another organization, they may export their data and then allow another organization to import it. Note that this creates a duplicate of the data and no changes will be tracked between the organizations after this.
To create an organization, a new user that wishes to be the organization administrator Signs Up to TimberID and instead of choosing an organization, selects the "Create New Organization" option.
Once you click Next you select the Name of your organization and fill out information about the Organization Administor, whose account will also be created.
Once you click Sign Up, your request must be approved by a Site Administrator as below:
See the [Managing Users](/timberid/user-guide/administration-guide/managing-users.md) section to understand the different user roles in TimberID and how to assign them
---
# 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://timberid.gitbook.io/timberid/user-guide/administration-guide/creating-organizations.md?ask=&goal=
```
`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.
