> For the complete documentation index, see [llms.txt](https://docs.terrakube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terrakube.io/2.33.0/user-guide/organizations/organizations.md).
# Creating an Organization
{% hint style="info" %}
Only users that belongs to Terrakube administrator group can create organizations. This group is defined in the terrakube settings during deployment, for more details see [Security](/2.33.0/getting-started/security.md#administrator-group)
{% endhint %}
Click the organizations list on the main menu and then click the **Create new organization** button
.png?alt=media)
Provide organization name and description and click the Create organization button
.png?alt=media)
Then you will redirected to the Organization Settings page where you can define your teams, this is step is important so you can assign the permissions to users, otherwise you won't be able to create workspaces and modules inside the organization.
{% hint style="info" %}
In order to start using your organization you must add at least one team. Terrakube will create some [default templates](/2.33.0/user-guide/organizations/templates/default-templates.md) but you can add more based on your needs. See [Creating a Team](/2.33.0/user-guide/organizations/team-management.md#creating-a-team) and [Templates](/2.33.0/user-guide/organizations/templates.md#creating-a-template) for further information.
{% endhint %}
---
# 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://docs.terrakube.io/2.33.0/user-guide/organizations/organizations.md?ask=&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.
.png?alt=media)