Troubleshoot protected document access

Check permission, record identity and protected storage without exposing a path.

What this guide covers

Check permission, record identity and protected storage without exposing a path. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Exact step-by-step process

1. Confirm the user has the required module permission.
2. Open the document from its parent record.
3. Use the application download/image route.
4. Check protected storage permissions if the file is retained but unreadable.

Fields, choices and supported possibilities

This action uses the values already stored on the selected source record. Review that record before continuing.

Code-backed validations and workflow rules

• Use the supported screen and permission; do not bypass validation or edit database records directly.

Expected result and verification

• The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.

Security, audit and operational checks

• Use the exact record and least-privilege role before changing any state.
• Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
• Use protected document and image routes rather than exposing server filesystem paths.
• Keep customer, driver, provider, financial and credential data within the authorised workflow.
• For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.

Related Courier guides