> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/general.md). # General - [Applications](https://docs.akenza.io/general/applications.md): akenza consists of four interlinked applications, each covering a different part of an IoT project. - [Tenants](https://docs.akenza.io/general/tenants.md): A tenant is a deployment of akenza. It holds organizations, and offers integrations and device type libraries to all of them. - [Deployment](https://docs.akenza.io/general/tenants/deployment.md): How an akenza Enterprise deployment is hosted: the deployment models, multi-region setups, and domains. - [Organization context](https://docs.akenza.io/general/organization-context.md): Where organizations sit in the akenza hierarchy, what belongs to one, and who can reach it. - [Workspace Context](https://docs.akenza.io/general/workspace-context.md): Where workspaces sit in the akenza hierarchy, what belongs to one, and what stays separate between them. - [Users](https://docs.akenza.io/general/users.md): How a user can belong to several organizations and workspaces, holding a different role in each. - [User Roles](https://docs.akenza.io/general/users/user-roles.md): A matrix of every akenza user role and the actions it permits, at both organization and workspace level. --- # 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.akenza.io/general.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.