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

# Occupancy settings

Define when a workspace is in use, so that occupancy figures ignore nights, weekends, and closed days.

Occupancy settings tell akenza when the space a workspace represents is actually in use. Hours outside that window are excluded from aggregations (by setting filter working hours on a dashboard component or when querying data using the akenza REST API), so a dashboard reports data during working time rather than averaging it across nights, weekends, and days the building was closed.

This matters because the two are very different numbers. A meeting room used solidly from 09:00 to 17:00 is fully utilized, but measured across the whole 24 hours it looks like a third empty.

{% hint style="info" %}
For what the resulting metrics mean, and the difference between concurrent and time-based occupancy, see [Occupancy monitoring](/analytics-use-cases/occupancy-monitoring.md).
{% endhint %}

## Working days and hours

<table><thead><tr><th width="200">Setting</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Working days</strong></td><td>The days of the week that count. Select the days that apply, for example Monday to Friday.</td></tr><tr><td><strong>Working hours</strong></td><td>The daily window that counts, given as <em>From</em> and <em>To</em>, for example 09:00 to 17:00.</td></tr><tr><td><strong>Lunch break</strong></td><td>Optional. A window inside working hours to leave out, for example 12:00 to 13:00.</td></tr></tbody></table>

Times are interpreted in the workspace time zone, which is set at the top of the [General settings](/device-management/managing-a-workspace/general-settings.md) page.

## Public holidays

**Exclude public holidays from occupancy aggregation** leaves out the public holidays of a regional calendar, shown next to the toggle as a region code such as `CH-ZH`. Select *View the list* to see exactly which dates will be excluded before you rely on it.

## Excluding and including specific days

Two further toggles handle the days a calendar cannot know about:

* **Exclude specific days.** Individual dates to leave out, such as a company shutdown between Christmas and New Year. Add one date per entry with *Add option*.
* **Include specific days.** Individual dates to count even though they would otherwise be excluded, such as a Saturday when the site was open for an event.

Included days take precedence, which is what lets you keep a normal working week while making a one-off exception.

{% hint style="warning" %}
Changing these settings changes how data is aggregated. Figures for a period may therefore differ from figures you read before the change, so it is worth agreeing the working pattern with whoever uses the dashboards before adjusting it.
{% 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/occupancy-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.