> For the complete documentation index, see [llms.txt](https://one-loop.gitbook.io/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://one-loop.gitbook.io/help/marketplace-apps/lexware-office/sicherheit-datenschutz-und-dokumente/sicherheitsmodell.md).

# Sicherheitsmodell

Jede geschützte Operation prüft serverseitig mehrere Ebenen:

1. gültiger CRM-Standort
2. gültige App-Installation
3. berechtigter Zugriff
4. aktive Lexware-Verbindung
5. richtige Mandanten- und Installationszuordnung
6. gültige und erwartete Eingabedaten
7. Schutz vor doppelter Dokumenterstellung

## Wiederholungen und Deduplizierung

Workflows und Webhooks können technisch wiederholt werden. Die App verwendet stabile Ereignis- oder Geschäftsreferenzen, damit ein Retry nicht unbeabsichtigt ein zweites Dokument erzeugt.

## Datei- und Linkzugriff

Datei-Links im CRM unterliegen den Zugriffsregeln des CRM-Kontakts. Direkte Lexware-Links erfordern weiterhin eine berechtigte Lexware-Sitzung.

## Supportfall

Teile im Fehlerfall:

* Zeitpunkt
* CRM-Standort
* Action oder Trigger
* Request ID
* angezeigten Error Code
* fachlichen Testablauf

Teile niemals:

* API-Schlüssel
* Bearer Token
* geheime App-Schlüssel
* vollständige Zugangsdaten


---

# 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://one-loop.gitbook.io/help/marketplace-apps/lexware-office/sicherheit-datenschutz-und-dokumente/sicherheitsmodell.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.