Two workers. One job.
Private pilot build. Real worker sign-in, phone camera and live Auth permission tests are NOT VERIFIED. No real workers have been invited.
What is connected
The delivery layer uses the existing Supabase person IDs, contractor memberships and work-order IDs. Hub projects and permanent zones are explicitly linked. Onboarding, invitations, actual time, submissions and office reviews are stored in Supabase with row-level permissions.
Before inviting anyone
- Verify Emanuel’s existing Supabase login and authorised office role. The inspected real account was not the director email and had no office role; no privilege was granted.
- Emanuel approves the two named participants and one job. Use individual accounts; do not share the director’s login. Configure private site access for those approved identities separately.
- Resolve or document the existing database security advisories and verify an isolated test environment. Staging was inactive at this checkpoint.
- In the existing hub, verify accepted quote/contract revisions, Dropbox root, controlled budget, zones and project-specific ITPs. A tender marked “accepted for estimating” is not a won job.
Office setup
- Open My Week, sign in with the verified office account, and choose Office.
- Workers sign in separately and submit Employee, Individual subcontractor or Contractor company onboarding. Contractors select an existing verified entity membership. Review references and missing information in the office queue.
- Link the hub project to the correct existing work order. The project starts on HOLD. Import each permanent zone and add instructions, material/PO references, target dates and ITP instance/revision references.
- Record each approved person’s invitation, zone restriction, role and expiry. This sends no email. Confirm scope, contract acceptance and mobilisation separately in the controlled process.
On each phone
- Open the private link in Safari or Chrome. Sign in with that worker’s own EGI account and accept only their personal job-access invitation.
- Check My Week, job, zone, instructions, target and ITP reference. Confirm the work release with the supervisor.
- Send one question, material request, inspection and deliberately selected job photo. Wait for saved confirmation; retain the original photo. Uploads stay in private intake until filed in Dropbox.
- Enter actual start, finish and every actual break. Append a correction with a reason; never overwrite the original.
- Office reviews each record, requests follow-up and files originals in Dropbox. Inspection review does not release a hold point; use the controlled ITP review.
Pass / fail checks
- Worker A cannot read Worker B’s private time or submissions, another job, or an unassigned zone.
- Wrong-person, expired and replayed invitations fail. Revoking access blocks the next read/write.
- A locked or pending account gets no job access. Workers cannot review onboarding, invite crew, create jobs or approve their own records.
- Photo retry does not duplicate the submission; download matches the original SHA-256. Test interrupted mobile connectivity and sign-out.
- Reconcile both workers’ records against office queues. Check correction history and original time/break records. No automatic payroll or lunch deduction.
Current limitations
Owner-private release; account provisioning and real invitations require the named approvals. Login sessions are held only in this page’s memory, so reloading requires sign-in. No offline queue, push notifications, automatic Dropbox filing, email monitoring, payroll rules or location collection. Original photo metadata is retained. Purchase-order and ITP references are linked; their approvals stay in the controlled hub. Use calls for urgent site matters.