> 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/device-management/managing-a-workspace.md).

# Managing a workspace

Create a workspace, manage the devices, data flows, and rules it holds, and configure the settings that apply to them.

**Workspaces** are where the actual work happens. Adding integration providers, data flows, and rules, or managing devices, are all activities that happen within a workspace. An organization can hold as many workspaces as you need, and every device belongs to exactly one of them.

The **workspace home** summarizes the state of the workspace: a [health score](/device-management/managing-a-workspace/health-score.md) with a short written assessment, the total device count, a breakdown of device status by online state, battery level, and signal quality, recent data processing, and the workspace metadata. [Genio](/genio/genio.md) can analyze the same picture and suggest what to do about it.

{% hint style="info" %}
For how workspaces sit between organizations and devices, see [Workspace Context](/general/workspace-context.md). For the level above, see [Managing an organization](/device-management/managing-an-organization.md).
{% endhint %}

## Create a workspace

To create a new workspace, select *Add workspace* on the workspaces page in your organization, or when switching workspaces.

![Create workspace](https://2165942204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMKXTFIN5ZlLOjBlfC4%2Fuploads%2F069WVHoS00CSWWXEOWo6%2Fscreely-1685008564662.png?alt=media\&token=3f27c56c-c685-47aa-bc82-a4ea67525384)

## What you manage in a workspace

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-microchip">:microchip:</i></td><td><strong>Devices</strong></td><td>The asset inventory of this workspace, where devices are created, imported, and inspected.</td><td><a href="/device-management/create-new-device.md">Devices</a></td></tr><tr><td><i class="fa-diagram-project">:diagram-project:</i></td><td><strong>Data Flows</strong></td><td>How uplinks are authenticated, decoded, and where the results are stored or forwarded.</td><td><a href="/device-management/your-data-flow.md">Data Flows</a></td></tr><tr><td><i class="fa-bolt">:bolt:</i></td><td><strong>Rules</strong></td><td>Business logic on incoming data, triggering notifications, downlinks, or aggregations.</td><td><a href="/device-management/rule-engine.md">Rules</a></td></tr><tr><td><i class="fa-cloud">:cloud:</i></td><td><strong>Integrations</strong></td><td>Connectivity provider accounts, used to connect, synchronize, and manage their devices.</td><td><a href="/device-management/integrations.md">Integrations</a></td></tr><tr><td><i class="fa-list-check">:list-check:</i></td><td><strong>Custom Fields</strong></td><td>Your own structured information on devices, such as a serial number or GPS coordinates.</td><td><a href="/device-management/managing-a-workspace/custom-fields.md">Custom fields</a></td></tr><tr><td><i class="fa-tag">:tag:</i></td><td><strong>Tags</strong></td><td>Groupings of devices, so that filters, dashboards, and rules can address them together.</td><td><a href="/device-management/managing-a-workspace/tags.md">Tags</a></td></tr></tbody></table>

Each of these lives in its own workspace, so devices, data flows, rules, and integrations in one workspace are invisible to another. Tags and custom fields are defined per workspace too, which is why a tag has to be unique only within the workspace that owns it.

Alongside them, the workspace navigation holds [Logs](/device-management/data-processing-logs.md) for inspecting what happened to incoming data, [Users](/device-management/managing-a-workspace/workspace-users.md) for access, and [General settings](/device-management/managing-a-workspace/general-settings.md). Whether a given page is accessible to you depends on your user role.

## Users and roles

A workspace has three roles: **admin**, **editor**, and **viewer**. Only **workspace admins**, and organization admins and owners, can invite users or change their roles. Every user listed on the workspace users tab shows both their organization and their workspace role.

Organization roles above member carry implicit access to all of that organization's workspaces, so a user can reach a workspace either directly or through the organization.

{% content-ref url="/pages/FblVKXEkBb8PUClw9HYL" %}
[Workspace Users](/device-management/managing-a-workspace/workspace-users.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MVvnykxZJF8KQPqkfwZ" %}
[User Roles](/general/users/user-roles.md)
{% endcontent-ref %}


---

# 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/device-management/managing-a-workspace.md?ask=<question>&goal=<user_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.