pn-new-crm/src/app/(dashboard)/[portSlug]/admin/documenso/page.tsx

import { CheckCircle2, Info } from 'lucide-react';

import {
  SettingsFormCard,
  type SettingFieldDef,
} from '@/components/admin/shared/settings-form-card';
import { DocumensoTestButton } from '@/components/admin/documenso/documenso-test-button';
import { PageHeader } from '@/components/shared/page-header';
import { Card, CardContent, CardHeader, CardTitle } from '@/components/ui/card';

const API_FIELDS: SettingFieldDef[] = [
  {
    key: 'documenso_api_url_override',
    label: 'API URL override',
    description:
      'Optional. Falls back to DOCUMENSO_API_URL env when blank. Bare host only — never include /api/v1; the client appends versioned paths based on the API version below.',
    type: 'string',
    placeholder: 'https://documenso.example.com',
    defaultValue: '',
  },
  {
    key: 'documenso_api_key_override',
    label: 'API key override',
    description: 'Optional. Falls back to DOCUMENSO_API_KEY env when blank. Stored in plain text.',
    type: 'password',
    defaultValue: '',
  },
  {
    key: 'documenso_api_version_override',
    label: 'API version',
    description:
      "Which Documenso REST API this port targets. v1 = Documenso 1.13.x stable. v2 = Documenso 2.x with the envelope model and richer per-field metadata. Test the connection after switching. See the v2 benefits card above for what changes when you flip this — and note that template-based EOI generation still uses the v1 formValues shape regardless of this setting (v2 template/use migration is on the roadmap).",
    type: 'select',
    options: [
      { value: 'v1', label: 'v1 — Documenso 1.13.x (default, stable)' },
      { value: 'v2', label: 'v2 — Documenso 2.x (envelope, recommended for new ports)' },
    ],
    defaultValue: 'v1',
  },
];

const SIGNER_FIELDS: SettingFieldDef[] = [
  {
    key: 'documenso_developer_name',
    label: 'Developer signer — name',
    description:
      'The party who signs after the client (typically the marina developer or owner). Used as the static "developer" recipient in templated documents (EOI). Was hardcoded as "David Mizrahi" in the legacy single-tenant system.',
    type: 'string',
    placeholder: 'David Mizrahi',
    defaultValue: '',
  },
  {
    key: 'documenso_developer_email',
    label: 'Developer signer — email',
    description: 'Email used to send the developer signing request via Documenso.',
    type: 'string',
    placeholder: 'dm@portnimara.com',
    defaultValue: '',
  },
  {
    key: 'documenso_approver_name',
    label: 'Approver — name',
    description:
      'The final approver who signs after the developer (typically a sales/legal lead). Was hardcoded as "Abbie May" in the legacy system.',
    type: 'string',
    placeholder: 'Abbie May',
    defaultValue: '',
  },
  {
    key: 'documenso_approver_email',
    label: 'Approver — email',
    description: 'Email used to route the final approval signing request.',
    type: 'string',
    placeholder: 'sales@portnimara.com',
    defaultValue: '',
  },
];

const EOI_FIELDS: SettingFieldDef[] = [
  {
    key: 'documenso_eoi_template_id',
    label: 'EOI Documenso template ID',
    description: 'Numeric template ID used by the Documenso EOI pathway.',
    type: 'string',
    placeholder: '12345',
    defaultValue: '',
  },
  {
    key: 'eoi_default_pathway',
    label: 'Default EOI pathway',
    description:
      'Which pathway is used when an EOI is generated without an explicit choice. Documenso = signed via Documenso, In-app = filled locally with pdf-lib.',
    type: 'select',
    options: [
      { value: 'documenso-template', label: 'Documenso template' },
      { value: 'inapp', label: 'In-app (pdf-lib)' },
    ],
    defaultValue: 'documenso-template',
  },
  {
    key: 'eoi_send_mode',
    label: 'Initial signing-invitation email behaviour',
    description:
      'Auto = the system sends our branded "please sign" email immediately when an EOI/contract/reservation is generated. Manual = the document is generated and the signing URL appears in the UI; a rep clicks "Send invitation" to dispatch. Auto is the lower-friction option for high-volume teams; manual lets reps review before sending. Applies to all document types, not just EOI.',
    type: 'select',
    options: [
      { value: 'manual', label: 'Manual (rep clicks Send after generation)' },
      { value: 'auto', label: 'Auto (send branded email on generate)' },
    ],
    defaultValue: 'manual',
  },
];

const CONTRACT_RESERVATION_FIELDS: SettingFieldDef[] = [
  {
    key: 'documenso_contract_template_id',
    label: 'Contract Documenso template ID (optional)',
    description:
      'Numeric template ID for sales contract generation. Leave blank to use the per-deal upload-and-place-fields flow instead (the typical path for contracts, since they are usually drafted custom per client).',
    type: 'string',
    placeholder: '',
    defaultValue: '',
  },
  {
    key: 'documenso_reservation_template_id',
    label: 'Reservation agreement Documenso template ID (optional)',
    description:
      'Numeric template ID for reservation agreements. Same logic — leave blank to upload per deal.',
    type: 'string',
    placeholder: '',
    defaultValue: '',
  },
];

const EMBED_FIELDS: SettingFieldDef[] = [
  {
    key: 'embedded_signing_host',
    label: 'Embedded signing host',
    description:
      "Origin of the public site that hosts the embedded Documenso signing pages. Outbound emails wrap raw Documenso signing URLs into {host}/sign/<type>/<token> so clients sign on your branded page rather than Documenso's domain. Leave blank to fall back to the app URL. Marketing-website pattern: https://portnimara.com",
    type: 'string',
    placeholder: 'https://portnimara.com',
    defaultValue: '',
  },
];

export default function DocumensoSettingsPage() {
  return (
    <div className="space-y-6">
      <PageHeader
        title="Documenso & EOI"
        description="API credentials, signer identities, and document generation behaviour. Use the test-connection button to verify a saved configuration before relying on it."
      />

      <Card>
        <CardHeader>
          <CardTitle className="flex items-center gap-2 text-base">
            <Info className="h-4 w-4" aria-hidden="true" />
            v1 vs v2 — what changes when you flip the API version
          </CardTitle>
        </CardHeader>
        <CardContent className="space-y-4 text-sm">
          <p className="text-muted-foreground">
            The CRM supports both Documenso 1.13.x (v1) and 2.x (v2). v1 is the default for
            backwards compatibility. v2 is recommended for new ports and unlocks the features
            below. Switching versions does <strong>not</strong> require any code changes —
            version-aware client methods pick the right endpoint per port. Switch, save, then run
            the test-connection button to confirm the chosen instance is actually on the matching
            Documenso version.
          </p>

          <div className="rounded-md border border-border bg-muted/40 p-3">
            <p className="mb-2 text-xs font-semibold uppercase tracking-wider text-muted-foreground">
              v2-only capabilities the CRM already uses when you pick v2
            </p>
            <ul className="space-y-1.5">
              <li className="flex items-start gap-2">
                <CheckCircle2 className="mt-0.5 h-4 w-4 flex-shrink-0 text-emerald-600" aria-hidden="true" />
                <span>
                  <strong>Bulk field placement.</strong> One API call per envelope vs. v1&apos;s
                  per-field POST loop. Faster contract generation, fewer transient retries on
                  multi-field uploaded contracts.
                </span>
              </li>
              <li className="flex items-start gap-2">
                <CheckCircle2 className="mt-0.5 h-4 w-4 flex-shrink-0 text-emerald-600" aria-hidden="true" />
                <span>
                  <strong>Percent-based field coordinates.</strong> No page-dimension lookup
                  needed — coordinates are portable across page sizes. v1 requires us to assume A4
                  for auto-placed fields.
                </span>
              </li>
              <li className="flex items-start gap-2">
                <CheckCircle2 className="mt-0.5 h-4 w-4 flex-shrink-0 text-emerald-600" aria-hidden="true" />
                <span>
                  <strong>Richer field metadata.</strong> TEXT labels &amp; required flags, NUMBER
                  min/max + format, CHECKBOX/DROPDOWN/RADIO option lists with defaults — all
                  ignored by v1, surfaced by v2 in the signing UI.
                </span>
              </li>
              <li className="flex items-start gap-2">
                <CheckCircle2 className="mt-0.5 h-4 w-4 flex-shrink-0 text-emerald-600" aria-hidden="true" />
                <span>
                  <strong>v2-flavoured webhook events.</strong> <code>RECIPIENT_VIEWED</code>,{' '}
                  <code>RECIPIENT_SIGNED</code>, <code>DOCUMENT_RECIPIENT_COMPLETED</code>,{' '}
                  <code>DOCUMENT_DECLINED</code>, <code>DOCUMENT_REMINDER_SENT</code> — all routed
                  through the same dedup + audit pipeline as v1 events.
                </span>
              </li>
              <li className="flex items-start gap-2">
                <CheckCircle2 className="mt-0.5 h-4 w-4 flex-shrink-0 text-emerald-600" aria-hidden="true" />
                <span>
                  <strong>Envelope/embed endpoints.</strong> <code>GET</code> and{' '}
                  <code>DELETE</code> go through <code>/api/v2/envelope/...</code> when v2 is
                  selected. Future embedded-signing iframe work will plug in here.
                </span>
              </li>
            </ul>
          </div>

          <div className="rounded-md border border-amber-200 bg-amber-50/60 p-3 dark:border-amber-900/40 dark:bg-amber-950/30">
            <p className="mb-2 text-xs font-semibold uppercase tracking-wider text-amber-700 dark:text-amber-400">
              v2 capabilities on the roadmap (not yet wired)
            </p>
            <ul className="space-y-1.5 text-muted-foreground">
              <li>
                <strong>Sequential signing</strong> (<code>signingOrder: SEQUENTIAL</code>) — would
                force client → developer → approver order on EOIs instead of all-at-once.
              </li>
              <li>
                <strong>Post-signing redirect URL</strong> (<code>redirectUrl</code>) — would land
                signed clients back on the portal rather than Documenso&apos;s page.
              </li>
              <li>
                <strong>Single-shot <code>/template/use</code></strong> (v2 prefillFields by ID
                replacing v1 formValues by name) — currently the EOI flow still uses the v1
                template path even when API version is v2. Needs per-template field-ID mapping in
                the template config before we can switch.
              </li>
              <li>
                <strong>Update envelope metadata</strong> (<code>/envelope/update</code>) — change
                title / subject / redirectUrl after creation without re-generating.
              </li>
              <li>
                <strong>Recipient roles beyond SIGNER</strong> (APPROVER / CC / VIEWER) — would let
                sales managers receive copies without a signature slot.
              </li>
            </ul>
            <p className="mt-2 text-xs text-muted-foreground">
              These items have no admin setting yet because they need code changes first. They
              live here so you know what&apos;s in the pipeline.
            </p>
          </div>
        </CardContent>
      </Card>

      <SettingsFormCard
        title="Documenso API"
        description="Per-port API credentials. Leave blank to use the global env defaults."
        fields={API_FIELDS}
        extra={<DocumensoTestButton />}
      />

      <SettingsFormCard
        title="Signers (developer + approver)"
        description="Identity of the static signers in your Documenso templates. The client is always pulled from the interest's linked client record; these values fill the developer (signing order 2) and approver (signing order 3) slots."
        fields={SIGNER_FIELDS}
      />

      <SettingsFormCard
        title="EOI generation"
        description="Default pathway, template, and email behaviour when an interest's EOI is generated."
        fields={EOI_FIELDS}
      />

      <SettingsFormCard
        title="Contract & reservation templates (optional)"
        description="Most ports leave these blank because contracts/reservations are drafted per deal and uploaded for signing. Set a template ID only if you have a standardised contract/reservation Documenso template."
        fields={CONTRACT_RESERVATION_FIELDS}
      />

      <SettingsFormCard
        title="Embedded signing"
        description="Where the public-facing branded signing pages live. The CRM rewrites Documenso signing URLs to point here when sending invitation and reminder emails."
        fields={EMBED_FIELDS}
      />
    </div>
  );
}