> 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/general-settings.md).

# General Settings

Settings that apply to a single workspace.

The **General** page of a workspace holds the settings that apply to that workspace and everything in it.

Modifying the settings requires the **Workspace Admin** role. Select *Save settings* to apply a change.

## Workspace basics

<table><thead><tr><th width="190">Setting</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>The workspace name, shown in the breadcrumb and in the workspace switcher. Often a project or a site, such as "Office Noerd".</td></tr><tr><td><strong>Description</strong></td><td>Optional free text, up to 500 characters. A street address is a common choice.</td></tr><tr><td><strong>Location</strong></td><td>The place the workspace represents. Select <em>Edit location</em> to set or change it.</td></tr><tr><td><strong>Time Zone</strong></td><td>The time zone the workspace operates in, for example (GMT+2) Europe/Zurich.</td></tr><tr><td><strong>Data retention</strong></td><td>How long data from this workspace is kept. <em>infinite</em> keeps it indefinitely.</td></tr></tbody></table>

{% hint style="info" %}
The workspace time zone is what dashboards group by. Day, week, and month boundaries in a [chart](/dashboard-builder/components/line-and-bar-chart.md) follow the workspace time zone rather than each viewer's browser, so everyone looking at the workspace sees the same buckets. It also defines the day boundaries used by [occupancy settings](/device-management/managing-a-workspace/general-settings/occupancy-settings.md).
{% endhint %}

{% hint style="warning" %}
Shortening **data retention** causes data older than the new period to be dropped. Forward anything you need to keep to a long-term destination with an [output connector](/device-management/your-data-flow/connectors.md) before reducing it.
{% endhint %}

## Sections

<table><thead><tr><th width="270">Section</th><th>What it controls</th></tr></thead><tbody><tr><td><a href="/device-management/managing-a-workspace/general-settings/device-lifecycle-reports.md">Lifecycle report</a></td><td>Daily or weekly email reports on device health, covering offline devices, weak signals, and low batteries.</td></tr><tr><td><a href="/device-management/managing-a-workspace/general-settings/workspace-properties.md">Workspace properties</a></td><td>A free-form JSON object of extra metadata, readable through the REST API.</td></tr><tr><td><a href="/device-management/managing-a-workspace/general-settings/occupancy-settings.md">Occupancy settings</a></td><td>Working days and hours, so that aggregations ignore the times the space is closed.</td></tr><tr><td><a href="/device-management/managing-a-workspace/general-settings/device-setup-assistant.md">Device Setup Assistant</a></td><td>The mapping file used when devices are configured on site.</td></tr><tr><td><a href="/device-management/managing-a-workspace/general-settings/actions.md">Actions</a></td><td>Deleting the workspace.</td></tr></tbody></table>

{% hint style="info" %}
[Tags](/device-management/managing-a-workspace/tags.md) and [custom fields](/device-management/managing-a-workspace/custom-fields.md) are also defined per workspace, but are managed on their own pages rather than under General.
{% 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/device-management/managing-a-workspace/general-settings.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.