Site photo gallery
Upload and review supported photos against the canonical site.
Site photos and documents
Keep project evidence beside the record it explains.
Upload private site photos and supported documents, then use them in the site, task, expense, DPR and report workflows where authorised people need their context.
The missing-context problem
A photo or file is difficult to trust when nobody knows which site record it supports.
Site evidence often arrives through personal galleries and message threads. The file survives, but its project, date, uploader and operational meaning become difficult to review.
A clear path from capture to responsible action.
Each step keeps the record, its context and the next responsibility visible.
- 01
Choose the project context
Start from the supported site or operational record that the evidence explains.
- 02
Upload the file
Add the supported photo or document through the canonical private-media workflow.
- 03
Review its record
Keep uploader, date and linked project context available to authorised people.
- 04
Use the evidence
Review it beside the task, expense, DPR or selected report where supported.
What photos and documents covers.
Focused capabilities for the complete workflow, described within their supported operating boundaries.
Private project documents
Keep supported documents behind authenticated, authorised access.
Workflow attachments
Attach evidence in supported task, expense, DPR and report contexts.
Controlled downloads
Use the existing signed-file access path instead of public media URLs.
Evidence in context
The current product shows photos entering the daily record and selected report.
Approved evidence shows the Today photo action and report preview. The underlying private document and site-photo surfaces are repository-evidenced, but no unsupported storage or document-control claim is added.
- Private media contract
- Site and workflow context
- Selected evidence in reports
A useful record has a responsible next person.
The feature supports the handoff without blurring who records, reviews or receives the information.
Supervisor
Capture supported site evidence close to the work it records.
Project manager
Review evidence with the operational record and decide what belongs in a report.
Client
See only the photos or document context deliberately included in a supported shared view.
Evidence boundary
NIYAM organises supported evidence; it does not certify the work shown.
Authorised people remain responsible for verifying physical progress, file relevance and the information selected for external sharing.
- No public-by-default files
- No unlimited-storage promise
- No full drawing or revision-control claim
Questions about photos and documents.
Straight answers about scope, review and responsibility.
Where can teams use photos and documents?
Supported files can appear in site, task, expense, DPR and report workflows according to the current contract and the user’s permissions.
Are uploaded files public?
No. Project media uses the current private-storage and authorised signed-access path unless an authorised user deliberately shares selected report content.
Is this full construction document control?
No. NIYAM supports project documents and evidence in operational workflows; it is not presented as a complete drawing, transmittal or revision-control system.