> 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-an-organization.md). # Managing an organization Create an organization, manage its users and roles, and configure the settings that apply across all of its workspaces. **Organizations** are shared accounts where businesses and projects can collaborate across many workspaces at once. Every setup of a device, every uplink received, and every user added to a workspace is linked to an organization. {% hint style="info" %} For how organizations sit between tenants and workspaces, see [Organization context](/general/organization-context.md). For the level below, see [Managing a workspace](/device-management/managing-a-workspace.md). {% endhint %} ## The organization home The **organization home** summarizes everything underneath the organization: * **Workspaces**, how many there are and their combined health score. * **Devices**, the total across all workspaces and how it is trending. * **Device health**, a breakdown by online status, battery level, and signal quality. * **About this organization**, its description, owner, organization ID, and when it was created and last edited. Below that are shortcuts into the [Dashboard Builder](/dashboard-builder/dashboard-builder.md), the [Device Setup Assistant](/device-setup-assistant/device-setup-assistant.md), and [Genio](/genio/genio.md), followed by your workspaces and dashboards, each of which can be searched, sorted, and opened directly. ## What belongs to an organization


Workspaces	The projects or sites in this organization, each holding its own devices, data flows, and rules.	Managing a workspace
Devices	Every device across all workspaces, in one list.	Devices
Data Fusion Layer	The semantic model of your sites, floors, zones, and assets.	Overview
Custom components	Logic blocks and device types you write once and reuse in any workspace.	Custom Components
API keys	Credentials for reaching akenza from your own applications.	API keys
Users	Who has access, and the role they hold across the organization's workspaces.	Organization Users

Custom components are the reason this level matters in day-to-day work: a [custom device type](/device-management/your-data-flow/device-type/device-type.md) or [logic block](/device-management/rule-engine/logic-blocks/custom-logic.md) belongs to the organization, so it can be written once and applied to devices in any of its workspaces. ## Create an organization During the signup process, you are asked to add an **organization** and a **workspace**. An organization name is typically the company name. Optionally a description and a logo can be added for recognizability. An organization can also be added later. Select *Switch Organization* at the top of the sidebar, then *New Organization*. ![Create organization](https://2165942204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MMKXTFIN5ZlLOjBlfC4%2Fuploads%2FjdqLPgU66XCRIpFuu1BL%2Fscreely-1685008462196.png?alt=media\&token=b556f584-b0aa-4aee-b870-475c1b03056a) {% hint style="info" %} Every organization belongs to a [tenant](/general/tenants.md), the akenza deployment it runs on. Tenant administrators can prevent tenant members from creating organizations of their own. {% endhint %} ## Users and roles An organization has the roles **owner**, **admin**, **editor**, **viewer**, and **member**. Adding users requires the **organization owner** or **admin** role, and the users tab lists everyone with the role they hold, regardless of which workspaces they were added to. Organization roles above member carry implicit access to every workspace in the organization, which is what makes them worth granting carefully. Only the **organization owner** can delete the organization or transfer ownership to another member. {% content-ref url="/pages/kIVoTDaFnfHZvMBE08Hj" %} [Organization Users](/device-management/managing-an-organization/organization-users.md) {% endcontent-ref %} ## Settings All organization-specific settings are managed from the organization settings group in the second-level navigation. Whether they are accessible to you depends on your user role.

Page	What it covers
General Settings	Name, description, owner, white labeling, Genio AI, organization properties, and deletion.
Billing & Subscription	The plan the organization is on and what it includes.
API keys	Credentials for the REST and WebSocket APIs.
Audit Logs	A record of what changed in the organization, and who changed it.
Users	Adding and removing users, and assigning roles.

--- # 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/device-management/managing-an-organization.md?ask=&goal= ``` `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.