> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/field-operations/inspection-reports/manage-tech-access.md). # Manage technician access to a report See who can access an inspection report, add technicians, or remove access without changing visit assignments. You need back office access and permission to edit inspection reports. > **Where to find it:** Inspection Reports → open a report → **Tech access → Manage**. You can also choose **Manage Tech Access** from the report's actions menu. ## Default access follows the property A technician assigned to a qualifying visit at a property can access **all inspection reports for that property**, including reports from other visits and reports without a visit. The business's technician history setting determines which assignments qualify. Upcoming assignments qualify too. For example, if only Tech A is assigned to a recent visit at a property, only A has default access. If A and B have recent visit assignments there, both can access that property's reports. Each technician's access lasts until their latest qualifying visit falls outside the history window. Assignment to another property does not grant access. The **Has access** list reflects actual report access. It shows **Assigned to visit** for the report's own crew, **Assigned at property** for another visit's crew, or **Added by …** for a manual grant. The same rules apply to the mobile Reports tab, direct links, report content, and saves. These rules apply to every report automatically. ## Add or remove a technician 1. Open **Manage** and use **Add tech** to search for a technician who needs access. 2. Choose **Remove** beside anyone who should lose access to this report. **Undo** reverses a pending addition or removal. 3. Click **Save**. Only your explicit changes are saved. **Cancel** discards them, and an unchanged list needs no save. Additions and removals appear in the report timeline. Manual additions have no expiration and apply only to this report. An explicit removal overrides the technician's property assignments for this report, even if they remain assigned or receive another visit there. Add them again to restore access. Other reports and technicians are unaffected. The controls work on drafts and submitted reports. Only active technicians with permission to view inspection reports appear. Their role still controls editing, publishing, and deletion. Back office users retain their usual permissions; removing every technician leaves back office access in place. ## When access expires Default access follows **Settings → Team → Technician App → Scheduling → Days in the past technicians can see**. A finite limit shows **Expires in … days** or **Expires tomorrow**. Expiration is based on the technician's latest assigned visit at the property, not the report's date, and happens at midnight in your business timezone. **No limit** means no expiration. When a technician creates or duplicates a report, their property-based access keeps its normal expiration. If they work through a manual grant instead of a qualifying visit assignment, the new report is granted to its creator without expiration. ## Related workflows Job Summaries and report-based quote/invoice prefills remain available to qualifying crews at the same property, even when different crews handled its visits. These workflows check every contributing report; an explicit removal or expired property access can block a workflow containing that report. Customer pages, deficiency lists, report history, common note suggestions, report-backed task activity, PDFs, attachments, Work Acknowledgments, and Improve Text references respect the same access. An attachment shared by several reports remains viewable through an accessible report, but editing it requires access to all its active reports. Deleted reports do not block edits to an attachment still used by an accessible report. Changes take effect when the app next connects and refreshes. Offline devices may still display previously downloaded content; the server rejects further saves after access ends. Previously downloaded or exported files cannot be recalled. If access or visit assignments change while the dialog is open, close and reopen **Tech Access** to review the latest list before saving. Related: [What the inspection report page shows](/field-operations/inspection-reports/what-the-inspection-report-page-shows.md) · [Fill inspection reports in the mobile app](/field-operations/mobile/fill-inspection-reports.md). --- # 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://learn.withessential.com/field-operations/inspection-reports/manage-tech-access.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.