# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [8.2. Model Link Plugin.](https://help.qseetech.com/part-8.-revit-model-preparation/8.2.-model-link-plugin..md)
- [3.2 Access Permissions Management](https://help.qseetech.com/part-3.-managing-access-and-user-permissions/3.2-access-permissions-management.md)
- [9.2 Shared Parameters Plugin.](https://help.qseetech.com/part-9.-organizing-the-model-data-structure/9.2-shared-parameters-plugin..md)
- [4.3. Parameter Mapping to Classifier Elements](https://help.qseetech.com/part-4.-parameters-and-data-classification./4.3.-parameter-mapping-to-classifier-elements.md)
- [3.1. Account Administration.](https://help.qseetech.com/part-3.-managing-access-and-user-permissions/3.1.-account-administration..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://help.qseetech.com/part-8.-revit-model-preparation/8.2.-model-link-plugin..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://help.qseetech.com/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://help.qseetech.com/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., `/part-8.-revit-model-preparation/8.2.-model-link-plugin..md`).

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