> 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/subscription.md). # Subscription Optional license settings for paid subscription The subscription page allows controlling the license on the server. A license key can be added and removed at any time without impacting an existing configuration. Other then the limitation of one organization there are no other resource limits on the free version. ### Subscription Features The subscription provides the features below. * Multi-tenant organizations. Create multiple isolated organizations for different teams within the same organization. This also provides access to the user-mode web console that provides only access to the specific organization resources that the authenticated user has access to. * Single sign-on authentication. Allows configuring multiple single sign-on providers including secondary authentication. Supported primary providers are Auth0, Azure Entra ID, Google Workspace, OneLogin, Okta and JumpCloud. Supported secondary providers are Duo, OneLogin Protect and Okta Verify. * Geo IP information. User sessions will load geo-ip information using a geo-ip service from MaxMind. This data can also be used to apply location restricted policies. --- # 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/subscription.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.