> For the complete documentation index, see [llms.txt](https://gitbook.clockin.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.clockin.de/english/getting-started-with-clockin/einrichtung-fuer-admins/set-permissions.md).

# Set Permissions

Define which areas and features the employee can view and use — both in the app and in the office dashboard.

## Here’s how:

1. Go to the employee’s profile and switch to the **Permissions** tab.
2. Decide what the employee can access when using the **office dashboard** by checking the relevant boxes for each section or feature. (☝️ *Common selections here include access to the browser-based time tracking, calendar, and dashboard. For department access, it’s usually best to select “No department”.)*
3. Define what features the employee can use in the **clockin app**. (☝️ *In most cases, all options are enabled here. One exception: “Correct own times” — this can be limited depending on your company policy.)*
4. Don't forget to click the Save Button.

{% hint style="info" %}
💡 Pro **Tip:**\
If you frequently assign the same permissions to multiple employees, it’s worth using **predefined roles**.\
This feature allows you to create custom permission profiles and assign them to several employees — no need to configure permissions one by one every time.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook.clockin.de/english/getting-started-with-clockin/einrichtung-fuer-admins/set-permissions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.