# Organization context Organizations are one level in the hierarchy of entities in the akenza ecosystem. Listed below is a hierarchically sorted list of entities: * Tenant * **Organization** * Workspace An organization on akenza is an entity to control access rights to workspaces, assets and data. Each organization contains one or more workspaces as well as one or more users. Organizations extend over all applications of akenza. Any given organization will extend over all applications it's subscription allows access to. Billing and subscription is managed on an organization level. See our [billing & subscription](/akenza.io/get-started/managing-an-organization/subscription.md) page for details. ### Users in an organization The following user roles exist in an organization: * Organization owner * Organization admin * Organization editor * Organization viewer * Organization member Refer to the [user roles page](/akenza.io/general/users/user-roles.md) for an overview of all user permission for each role. A user with access to at least one workspace in an organization will show up as organization-member. A user with organization specific rights higher than member has corresponding access right to all workspaces of the organization. ### Usage examples: Organizations on akenza often reflect business organizations, companies or organization units. Tenant managers with the intention of reselling the akenza platform may chose to onboard their customers as organizations on akenza. Thus strictly isolating devices and data of individual customers. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.akenza.io/akenza.io/general/organization-context.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.