> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/timesheets/set-up-employees-and-working-hours.md).

# Set up employees and working hours

Before employees register hours, first set up their availability.

That availability defines the default work week and helps process hours correctly.

{% stepper %}
{% step %}

### Open Timesheets

Log in to the **OutSmart BackOffice**.

Go to **Timesheets** in the left menu.
{% endstep %}

{% step %}

### Check the employee overview

The module opens with an overview of all employees.

New employees are often set to a default work week of **40 hours**.
{% endstep %}

{% step %}

### Open the employee settings

Go to **Settings → Employees** in the bottom-left corner.

Click **Edit** for the employee you want to change.
{% endstep %}

{% step %}

### Set the availability

Scroll to **Availability**.

Set the working hours per day.

You can also set evening hours and weekends.
{% endstep %}

{% step %}

### Save the changes

Click **Save**.

The configured hours then become visible in Timesheets.
{% endstep %}
{% endstepper %}

### Practical tips

* Set part-time schedules directly per day.
* Use separate times for evening or weekend shifts.
* Always check new employees before they submit hours.

### What this affects

Availability helps with:

* recognizing regular working hours
* separating overtime or exceptional hours
* better post-calculation per employee


---

# 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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/timesheets/set-up-employees-and-working-hours.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.