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

# Workspace Context

Where workspaces sit in the akenza hierarchy, what belongs to one, and what stays separate between them.

Workspaces 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 workspace runs on
* [Organization](/general/organization-context.md)
* **Workspace**

A workspace on akenza is an entity to control access rights to assets and data. Each workspace contains one or more users, and each workspace is assigned to exactly one organization.

Workspaces extend over all applications of akenza. Any given workspace will extend over all applications its corresponding organization's subscription allows access to.

Billing and subscription are handled at organization level. Workspaces inherit access to features from the organization they belong to. See our [Billing & Subscription](/device-management/managing-an-organization/subscription.md) page for details.

## What belongs to a workspace

A workspace is the boundary for the day-to-day objects of an IoT project:

<table><thead><tr><th width="220">Object</th><th>Scope</th></tr></thead><tbody><tr><td><a href="/device-management/create-new-device.md">Devices</a></td><td>Every device is assigned to exactly one workspace.</td></tr><tr><td><a href="/device-management/your-data-flow.md">Data flows</a></td><td>Defined in a workspace and applied to the devices in it.</td></tr><tr><td><a href="/device-management/rule-engine.md">Rules</a></td><td>Act on the data of devices in the same workspace.</td></tr><tr><td><a href="/device-management/integrations.md">Integrations</a></td><td>A connectivity provider account is linked per workspace.</td></tr><tr><td><a href="/device-management/managing-a-workspace/custom-fields.md">Custom fields</a></td><td>Defined per workspace and available on its devices.</td></tr><tr><td><a href="/device-management/managing-a-workspace/tags.md">Tags</a></td><td>Defined per workspace, and unique within it.</td></tr></tbody></table>

Objects in one workspace are not visible from another, which is what makes a workspace a useful unit of separation. It is also why a tag only has to be unique within the workspace that owns it, and why moving work between workspaces means recreating rather than sharing.

{% hint style="info" %}
Dashboards are the exception. They are managed at organization level, so one dashboard can draw on devices from several workspaces, as long as you have access to them. See [Applications](/general/applications.md).
{% endhint %}

{% content-ref url="/pages/-MO5H-sO9l8N2tO7n0vw" %}
[Managing a workspace](/device-management/managing-a-workspace.md)
{% endcontent-ref %}

## Users in a workspace

Every user on akenza is a member of at least one workspace. The following roles exist:

* Workspace admin
* Workspace editor
* Workspace viewer

Access rights to a workspace do not extend to the parent organization. Organization roles, on the other hand, carry implicit workspace roles for all of that organization's workspaces. The rights of each role are described in detail on the [user roles page](/general/users/user-roles.md).

## Workspace settings

Each workspace carries its own settings, including its time zone, data retention, occupancy working hours, and device lifecycle reports. The time zone in particular is worth setting deliberately, because dashboards group data by the workspace time zone rather than by the viewer's.

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

## Usage example

Workspaces on akenza may represent a number of real world entities, including but not limited to the following:

* Organization units
* Buildings
* Factories
* Vehicles
* Locations
* Fleet of sensor devices
* Individual use cases

Organizations on akenza may decide to use workspaces to give access to devices and data to a subset of their organization members. You may assign devices and users to workspaces that represent your specific business needs.


---

# 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/workspace-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.