Setup guide

Pipeline name: Davick Team Onboarding

1. 1Invited
2. 2Form Submitted
3. 3Documents Pending
4. 4Jibble Pending
5. 5Ready to Start
6. 6Active
7. 7Completed

The custom field Onboarding Stage mirrors these stage labels so workflow filters can move contacts through the pipeline.

• • Personal information: Full name, Email, WhatsApp, Country, Position, Start date.
• • Collaboration: Trial period, Work schedule, Compensation (PHP), Responsibilities.
• • Policies acknowledgment (required).
• • Documents: CV submitted, Confidentiality acknowledgment, Contract reviewed (all required).
• • Jibble: display the administrator-provided invitation link + a registration confirmation checkbox.
• • On submit, the contact is created/updated in the CRM with all custom fields via the connected tracking endpoint.

1. Trigger: Form submitted (davick-contractor-onboarding) — fires on the tracking event this app sends.
2. Step 1 — Welcome email: send a branded welcome email with the onboarding instructions and Jibble invitation link to the contractor.
3. Step 2 — Pipeline update: move the contact into Davick Team Onboarding at the “Form Submitted” stage, then to “Documents Pending”.
4. Step 3 — Admin notification: send an internal notification (email/SMS) to the administrator when documents are submitted and again when Jibble registration is confirmed.
5. Step 4 — Status sync: update the pipeline stage to “Jibble Pending”, then “Ready to Start” once the contractor confirms Jibble registration (read the Jibble Registered custom field).

• ☐ Verify documents (CV, confidentiality/NDA, contract).
• ☐ Verify Jibble registration is active.
• ☐ Grant project / sub-account access and tooling.
• ☐ Promote pipeline stage to “Active”.
• ☐ Mark “Completed” once the first task is underway.

Checklist state persists in Cloud, so any administrator returning to the board on any device sees prior progress — and contractors never see these fields.

Jibble status follows the record state. A contractor moves through these states:

1. • An administrator pastes the official Jibble team invitation link on the Admin board (per contractor).
2. • The contractor clicks Join Davick on Jibble on the Jibble step and creates their account.
3. • The contractor checks the box confirming registration (status → Pending Verification).
4. • The administrator confirms the contractor appears in the Davick Jibble organization using Open Jibble, then checks the admin verification box (status → Active).

Nothing here calls the Jibble API and nothing auto-verifies registration — the admin check is a manual confirmation. A future secure Jibble API integration (server-side, credentials in Cloud secrets) can automate the verify membership step; the architecture is stubbed in src/lib/jibble.ts.

Open your Jibble organization

• • Sign-in uses real Cloud email/password accounts. New accounts require email verification before they can sign in.
• • Every new account starts as a contractor by default — the platform's default, non-admin access tier. The admin role is never inferred from an email and is never set by the user themselves.
• • Admin roles are granted only through a secure, administrator-controlled path: an existing admin uses the Administrator access panel on the Admin board (or a one-time operator grant via Cloud SQL). Use this to promote your first administrator after creating their account.
• • The Admin board (/admin) is restricted to the admin role; a signed-in contractor sees an “admins only” notice.
• • Contractors (/onboarding) see and update only the onboarding record bound to their own email. Cloud RLS blocks reads/writes of any other record; a BEFORE UPDATE trigger blocks contractors from touching admin-only fields (document/Jibble/project checks) or promoting to Active / Completed.
• • Records, Jibble links, and checklist state persist in Cloud — across devices and sessions. No data is stored in the browser.