> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation/reports/import-plextrac-report.md).
# Importing a Report
PTRAC files (.ptrac) can be imported into PlexTrac for cross-team collaboration. For instance, a red team from one tenant can share with a blue team client with its own PlexTrac instance.
Reports can be imported either in the **Client** module or the **Reports** module. The instructions below are specific to the **Reports** module, assuming the user has an exported report in PTRAC format.
## Importing Permissions
Admins can configure the options to import files via the **Admin Dashboard** on the "Role Based Access" page. To do so, select a custom role and click the "Ability to import reports" button under Reports Permissions. A dialog box will appear with options to turn on/off the ability to import reports.
## Importing a Report
Step 1: From the **Reports** module home page, click **Import Report**.
Step 2: Select the client the report will be associated with from the pulldown menu on the modal.
Step 3: Drag the .ptrac file to the box provided or click the box and navigate to the file on the computer.
Step 4: Click **Submit**.
A progress bar will indicate the status; the upload may take a minute or two.
When completed successfully, a confirmation message will appear.
---
# 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.plextrac.com/plextrac-documentation/product-documentation/reports/import-plextrac-report.md?ask=&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.
