> For the complete documentation index, see [llms.txt](https://docs.pritunl.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pritunl.com/kb/cloud/components/organizations.md).
# Organizations
Resource groups for multi-tenant configurations
Organizations allow isolating resources for multi-tenant use cases. This is intended for trusted teams within one company not for providing untrusted users access to a Pritunl Cloud environment. There is not sufficient controls on resources to allow potentially malicious users to access the Pritunl Cloud web console. This feature requires an active subscription.
### Node Configuration
To enable multi-tenant access with organizations enable both the *Admin* and *User* option in the node settings. Then set the domain to use for admin access and the domain for user access. This subdomains should be under the same domain. Users can then login to the user web console at the configured domain. If the user has access to multiple organizations a selection will be shown on the left side of the navigation bar to switch organizations.
### Organization Roles
Users are provided access to organizations based on matching roles. If one of the user roles matching one of the organization roles the user will have access to that organization. These users should be created as non-administrator accounts. Only administrator accounts have access to the full web console with access to all resources.
---
# 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.pritunl.com/kb/cloud/components/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.
