> 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/how-to-create-a-working-environment.md). # Getting Started Set up your akenza working environment, then connect your first device and see its data arrive. Everything in akenza lives inside a **working environment**: an organization that represents your account, and at least one workspace inside it where the actual work happens. You create both during registration, in a single dialog. {% hint style="info" %} No account yet? Sign up at [app.akenza.io](https://app.akenza.io). No hardware yet? The [Device Simulator](/device-management/create-new-device/device-simulator.md) lets you complete this whole guide without a physical device. {% endhint %} ## Organizations and workspaces

Level	What it is	What you manage here
Organization	The account under which a business collaborates across many workspaces at once. Usually named after your company.	Billing and subscription, API keys, users, audit logs, white labeling
Workspace	A container inside an organization, typically one per project or site.	Devices, data flows, rules, custom fields, tags

An organization can hold as many workspaces as you need, and you can switch between them at any time. Above the organization sits the [tenant](/general/tenants.md), the akenza deployment itself. On the public cloud every organization shares the same tenant; an Enterprise deployment is a tenant of its own. ## Create your working environment {% stepper %} {% step %} ### Create an organization During registration you are asked to create an organization. Give it a name, which is most likely your company name, and optionally a description and a logo. Select *Next* to continue.

The Create new Organization dialog, showing the Organization step and the Workspace step that follows — Creating an organization

To add further organizations later, select *Switch Organization* at the top of the sidebar, then *New Organization*. {% endstep %} {% step %} ### Create a workspace The same dialog continues with the **Workspace** step, so a new organization never ends up empty. Workspaces are where the actual work happens: adding data flows, rules, and managing devices. A suitable workspace name is, for example, the name of your project or the site you are equipping. Select *Create Workspace* to finish. You land on the organization overview, from where you can enter your new workspace.

{% endstep %} {% step %} ### Connect your first device With a workspace in place, you are ready to create a data flow and a device, and to watch the first uplink arrive. {% content-ref url="/pages/-MUICr3a0-fo8AuI\_EKB" %} [Connect a Device](/how-to-create-a-working-environment/how-to-connect-a-device.md) {% endcontent-ref %} {% endstep %} {% endstepper %} ## What to do next akenza tracks your progress through a **Quick start** checklist on the organization home: data flow created, device created, data received, and rule set up. The guide above plus [Connect a Device](/how-to-create-a-working-environment/how-to-connect-a-device.md) covers the first three. From there:


Set up a rule	Trigger notifications, downlinks, or aggregations from incoming data.	Rules
Build a dashboard	Visualize your data and share it with a public link.	Overview
Add devices in bulk	Onboard a whole fleet from a CSV file instead of one device at a time.	Bulk actions
Invite your team	Add co-workers to your organization and assign their roles.	Users

{% hint style="info" %} Learn more about managing your working environment in [Managing an organization](/device-management/managing-an-organization.md) and [Managing a workspace](/device-management/managing-a-workspace.md). {% endhint %} --- # 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/how-to-create-a-working-environment.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.