Owner: Partnerships / Growth (platform admin) | Review: Quarterly

A partner moves through a tracked, auditable pipeline: admin sends a tokenised proposal, the partner reviews it (engagement is tracked per section), the partner self-signs an NDA to unlock the document vault, and the admin works the relationship on a kanban until the deal is closed and the partner is activated. Every external touch is logged to a timeline, and NDA signatures carry an Oman Electronic Transactions Law evidence chain.

Pipeline stages

The real status enum (partners.status) — note the proposal comes before the NDA, and the NDA is partner-initiated, not emailed for signing:

draft → proposal_sent → meeting_scheduled → nda_signed → mou_signed → active
                                                                         ↘ on_hold (lost / stalled)

Tracked in Admin → Partnerships (kanban, one column per status; drag a card to move it).

Step-by-step

Create partner & issue a proposal token

Create the partner record, then `issueProposalToken` mints a signed **30-day JWT**. Prefer tokens over legacy access codes (codes are deprecated, accepted only while `LEGACY_PROPOSAL_CODES_ACCEPTED=true`). Status: `proposal_sent`.

Send the invitation

`sendInvitation` emails a branded message with the token proposal link and the Cal.com booking link. Logged to the timeline.

Partner reviews the proposal (tracked)

Partner opens `/partnership/:id?token=…` — content is **server-only** (never shipped before unlock). An IntersectionObserver fires `trackView` per section (hero, terms, metrics, value, modules, why, next_steps, cta, documents) with time-on-section. First open triggers an admin first-view alert; the kanban card shows the view count. Full vault stays NDA-gated.

Partner signs the NDA

Partner goes to `/sign/:id/nda` — 4 steps: contact info → review the bilingual (EN/AR) NDA (scroll-to-unlock) → typed signature → confirmation (ref `NDA-00001`). `submitNda` records a `partnerNdaRequests` row (validity **+3 years**), captures **IP + User-Agent** (Oman Electronic Transactions Law, RD 69/2008), writes an `nda_signed` timeline entry, auto-creates a "NDA — Signed" vault document, **auto-advances status to `nda_signed`**, and sends dual emails (admin alert + signer's official record).

Grant portal access

`sendPortalAccess` emails the `/portal/{token}` link — a deterministic **HMAC-SHA256 token link** (no password/credentials). The partner sees the timeline, NDA history, vault documents (download-audited), and action items they can mark done.

Work the pipeline & close

On the kanban: `addMeeting` logs a meeting and auto-creates action items + an agenda email; `addAction` / `addDecision` capture follow-ups. Move `nda_signed → mou_signed` (stamps `mouSignedAt`). `closeDeal('won')` → `active`; `closeDeal('lost'|'stalled')` → `on_hold`. On `active`, the NDA vault gate lifts and the timeline becomes the operational log.

NDA evidence chain

Each signature is stored with enough to stand up under Oman's Electronic Transactions Law:

Rate limits: proposal unlock 5 attempts/hr/IP; NDA submit 3/hr/IP.

Live partners

mol · mocipi · occi · ooredoo · bank-sohar · usman — content lives in server/data/partnership-content.ts (server-only).

Failure modes

Key files