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, the akenza deployment the workspace runs on

• Organization

• 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 page for details.

What belongs to a workspace

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

Object	Scope
Devices	Every device is assigned to exactly one workspace.
Data flows	Defined in a workspace and applied to the devices in it.
Rules	Act on the data of devices in the same workspace.
Integrations	A connectivity provider account is linked per workspace.
Custom fields	Defined per workspace and available on its devices.
Tags	Defined per workspace, and unique within it.

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.

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.

Managing a workspace

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.

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.

General Settings

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.