Client reports: viewing, locks, and links (for internal staff)

Use this guide to understand what clients experience when opening report links, especially when they see Report Locked instead of report content.

Written By Ryan Wagner

Last updated About 1 month ago

Where to find it

Clients usually open reports from the job portal, from a direct report link sent by your team, or from portal-related email/SMS links.
Staff can reproduce the client path by opening the client portal/report flow from the workorder.

A client says they cannot open their report.
A client sees Report Locked and asks what to do next.
Staff need to confirm whether the issue is access/requirements vs publishing/report availability.

When a client opens a report link, Attik shows one of two outcomes:

Clients see:

Title: Report Locked
Job/property context (when available)
A lock explanation message (why access is blocked right now)
A clear next-step button, such as returning to the portal to complete required actions

Typical reasons include unmet prerequisites such as required payment/signing or report availability/publication rules.

Clients see the full report page and can read report sections normally (desktop/mobile layouts vary by device and report type).

Tell the client to read the exact lock message shown on their page; that message is the most accurate next-step guidance.
If the message points to completing portal actions, direct them back to the job portal first.
If they already completed the required action but still see locked state, verify job/report status internally and then retest the same link.

Report links should only be shared with authorized contacts for that job.
Forwarding a locked report link does not bypass requirements; recipients will still see Report Locked until prerequisites are met.

Lock behavior can vary by job setup, permissions, and publication/payment/agreement state.
Demo/sample contexts may not behave exactly like live client jobs.