> 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/organization-context.md).

# Organization context

Where organizations sit in the akenza hierarchy, what belongs to one, and who can reach it.

Organizations are one level in the hierarchy of entities in the akenza ecosystem. Listed below is a hierarchically sorted list of entities:

* [Tenant](/general/tenants.md), the akenza deployment the organization runs on
* **Organization**
* [Workspace](/general/workspace-context.md)

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 its subscription allows access to.

Billing and subscription are managed at organization level. See our [Billing & Subscription](/device-management/managing-an-organization/subscription.md) page for details.

## What belongs to an organization

An organization is the level at which access, identity, and anything shared between projects is decided:

<table><thead><tr><th width="230">Object</th><th>Scope</th></tr></thead><tbody><tr><td><a href="/device-management/managing-a-workspace.md">Workspaces</a></td><td>Every workspace is assigned to exactly one organization.</td></tr><tr><td><a href="/device-management/create-new-device.md">Devices</a></td><td>Belong to a workspace, but can be listed and searched across the whole organization.</td></tr><tr><td><a href="/device-management/custom-components.md">Custom components</a></td><td>Custom device types and logic blocks are defined once here and usable in any workspace.</td></tr><tr><td><a href="/dashboard-builder/dashboard-builder.md">Dashboards</a></td><td>Managed at organization level, so one dashboard can combine devices from several workspaces.</td></tr><tr><td><a href="/data-fusion-layer/data-fusion-layer.md">Data Fusion Layer</a></td><td>The semantic model of sites, floors, zones, and assets.</td></tr><tr><td><a href="/device-management/managing-an-organization/api-keys.md">API keys</a></td><td>Issued per organization and scoped to it.</td></tr><tr><td><a href="/device-management/managing-an-organization/audit-logs.md">Audit logs</a></td><td>A record of changes across the organization.</td></tr><tr><td><a href="/device-management/managing-an-organization/organization-users.md">Users</a></td><td>Access is granted here or in an individual workspace.</td></tr></tbody></table>

The division is worth keeping in mind when deciding where to put something. Objects used in day-to-day operation of one project, such as devices, data flows, rules, integrations, tags, and custom fields, belong to a [workspace](/general/workspace-context.md). Anything shared between projects, or that concerns who may see them at all, belongs to the organization.

{% content-ref url="/pages/SwWd28hSdtf5reOYIkXR" %}
[Managing an organization](/device-management/managing-an-organization.md)
{% endcontent-ref %}

## 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](/general/users/user-roles.md) for an overview of all user permissions 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 rights to all workspaces of the organization, including workspaces created later. Access granted in a single workspace never extends upward to the organization.

{% hint style="info" %}
Only the **organization owner** can delete the organization or transfer ownership, and an organization has exactly one owner at a time.
{% endhint %}

## Organization settings

Each organization carries its own settings, including [white labeling](/device-management/managing-an-organization/general-settings/white-labeling.md), whether [Genio AI](/device-management/managing-an-organization/general-settings/genio-ai.md) is active, and its [subscription](/device-management/managing-an-organization/subscription.md). Because subscription is held here, workspaces inherit the features available to them from the organization they belong to.

{% content-ref url="/pages/eOXw478KABqwFuIjT9ms" %}
[General Settings](/device-management/managing-an-organization/general-settings.md)
{% endcontent-ref %}

## Usage examples

Organizations on akenza often reflect business organizations, companies or organization units.

Resellers of the akenza platform may choose to onboard their customers as organizations on their [tenant](/general/tenants.md), strictly isolating the devices and data of individual customers. Combined with [white labeling](/device-management/managing-an-organization/general-settings/white-labeling.md), each customer sees a platform carrying the reseller's branding rather than akenza's, and a [tenant integration](/general/tenants.md#tenant-integrations) lets them all onboard devices onto the reseller's own network.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.akenza.io/general/organization-context.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.