> For the complete documentation index, see [llms.txt](https://docs.interaktifotel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interaktifotel.com/en/administration/staff-and-permissions.md).

# Staff and permissions

Open Staff Definitions and System Logs.

## Set up a staff account

1. Open Staff Definitions using an authorized account.
2. Create a staff member or edit an existing person.
3. Complete identity, login and displayed staff information.
4. Assign the role and property access appropriate for the job.
5. Save and verify that the employee can sign in to the correct business with their own card.

Do not share one account among multiple employees. Personal accounts identify who performed each operation and keep preferences separate.

## A menu or action is missing

Check the employee's role and property access. Changing the role alone may not grant access to another property. Updating or deleting a staff account may terminate open sessions, requiring the person to sign in again.

## Find a change in System Logs

1. Open System Logs.
2. Filter by the relevant period, operation or record using the available controls.
3. Inspect the operation summary, room/property and staff member.
4. Compare before-and-after values and read any cancellation or renovation reason.

Failed operations do not create successful-change records. Details missing from older records are not reconstructed. Logs are not an undo tool; make corrections through the relevant editing or cancellation workflow.


---

# 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://docs.interaktifotel.com/en/administration/staff-and-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.