> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/organisation/what-is-an-organisation.md). # What is an organisation? An organization is a home for all content that will be created on Whaly, imagine it as a library where all your content is stored. An organization is plugged on a Warehouse where your data lives. It'll store all your models, sources, dashboards, questions... You can have access to multiple organizations for different purposes: * When you want to have multiple different Warehouse * When you want to have a "Training Sandbox" to test a few things without ta * For testing purposes of new features * If you're invited by another company to collaborate on their environment ### How to switch between organization? If you have access to multiple orgs you can switch org by clicking on your **profile picture** and then on **Change Organization**.

--- # 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.whaly.io/organisation/what-is-an-organisation.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.