> For the complete documentation index, see [llms.txt](https://docs.qapilot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qapilot.io/detailed-documentation/reports/report-sharing-deep-links.md).
# Report Sharing, Deep Links
## Report Sharing
Security report links can be shared via email and support secure, direct access through authentication.
Email reports include a link that redirects users to the login page when required and automatically returns them to the specific security report after successful authentication. If the user is already logged in, the system bypasses the login step and opens the report directly.
For users who are authenticated but do not have access to the associated project, a dedicated error screen is shown with an appropriate message. Authorised users are always redirected seamlessly to the intended report view.
This update improves usability while maintaining access control and security.
***
## Deep Links
The **Deeplink section** in QApilot Reports displays the results of all executed deep links within a test run. It helps verify that each deep link correctly navigates to its intended screen and that associated login or logout flows execute successfully.
### **Key Components**
* **Deeplink Summary:** Shows the deep link URL, start time, total execution time, status, and a screenshot of the landing screen.
* **Execution Logs:** Lists step-by-step actions (e.g., click, find element, wait) performed during the deep link execution with timestamps and outcomes.
* **Linked Test Cases:** If the deep link triggers login or logout test cases, they are shown as separate expandable sections with their own execution logs and statuses.
This section provides a complete, traceable record of deep link validation, ensuring accurate navigation, correct page loads, and reliable authentication flows.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.qapilot.io/detailed-documentation/reports/report-sharing-deep-links.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.