> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/basic-concepts/organizations.md). # Organizations Threekit is a multi-tenant application, providing a shared platform for all of its customers. An Organization is a way to create segmentation within the platform. Every Threekit customer is an Organization. Threekit does not allow for nested Organizations. Users must be members of an Organization to access the Organization's data. Users can be members of multiple Organizations and may switch between Organizations within the portal. This feature is intended for Threekit, its implementation Partners who manage multiple Customer accounts, or modeling partners who contract with multiple Threekit Customers. #### Multiple Threekit Organizations As stated above, there may be some customers who maintain multiple Organizations, there may also be 3D modelers who provide visuals for more than one customer. --- # 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://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/basic-concepts/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.