Company membership comes first.
Workspace access checks the signed-in user’s active membership and role. Company isolation keeps records tied to their owning workspace.
The right people.
The right job records.
A crew member capturing proof and an office reviewer approving it have different responsibilities. JobPacket keeps that distinction in the workflow.
WORKSPACE ACCESS MODEL
Your company workspace
FIELDAssigned workCapture & submit
OFFICEReview workflowReview & approve
Private job records & media
Media belongs with the job.
Job photos use private storage and temporary access links. The capture and review workflow controls who can reach the evidence.
Approval has a history.
Approved packet versions preserve the evidence reviewed at that point. Later work creates a new version rather than silently replacing the earlier approval.
Make the data responsibilities clear.
Operator details, hosting arrangements, retention, deletion responsibilities, and access terms must be confirmed before real customer data is introduced. Account-deletion requests are supported in the app workflow; the final service policy is still being verified.
Read the current privacy notice
A FEW GOOD QUESTIONS
Before you get started.
Does JobPacket have a published compliance certification?
No certification is claimed here. This page describes implemented access controls and review behavior, not an independent security certification.
Can everyone in the company approve work?
No. The product distinguishes field capture from office review through workspace roles. Setup should confirm who owns each responsibility.
Can I put customer data into this website demo?
The sample interfaces are illustrations. The job checklist builder runs locally in your browser; use sample workflow details and leave out sensitive customer information.
PUT IT TO WORK
See it in action
Define the workflow. Define the access.
Start with one job, one crew, and the proof your office needs.