# Page Not Found

The URL `pages/NfS1hUD6JDGFzxZYcdaI` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [General settings introduction](https://doc.wearepatchworks.com/product-documentation/general-settings/general-settings-introduction.md)
- [Accessing your company profile](https://doc.wearepatchworks.com/product-documentation/company-management/accessing-your-company-profile.md)
- [Error reporting & exception handling](https://doc.wearepatchworks.com/product-documentation/process-flows/error-reporting-and-exception-handling.md)
- [Viewing all users for your company profile](https://doc.wearepatchworks.com/product-documentation/users-roles-and-permissions/viewing-all-users-for-your-company-profile.md)
- [Patchworks advanced analytics](https://doc.wearepatchworks.com/product-documentation/company-management/company-insights/patchworks-advanced-analytics.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://doc.wearepatchworks.com/product-documentation/general-settings/general-settings-introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://doc.wearepatchworks.com/product-documentation/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://doc.wearepatchworks.com/product-documentation/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/product-documentation/general-settings/general-settings-introduction.md`).

You may also use `Accept: text/markdown` header for content negotiation.