Confirm Page & Main Access Flow

[mahid797]

Goal

Implement a two‐step UI flow using page.tsx (the disclaimers/confirm button screen) and AccessPage.tsx (the main logic). The workflow must handle dynamic JSON visitor fields, a possible password, and direct‐access scenarios.

Detailed Guidelines

1. page.tsx:

   • Render disclaimers, branding, a “Confirm” button.
   • Clicking confirm either toggles local state or navigates to a sub‐route.
   • This ensures a dedicated disclaimers step.

2. AccessPage.tsx:

   • Calls useDocumentAccess(linkId) to get link details:
     • visitorFields (JSON),
     • passwordProtected,
     • nameRequired, emailRequired (though these are columns, the server might also reflect them in the JSON).
   • If the link is invalid/expired → show <AccessError />.
   • If the link is truly public (no required fields, no password) → do Direct‐access → get signedUrl → show <FileDisplay />.
   • Otherwise, show <VisitorInfoModal /> to collect data.

3. No References to old numeric flows (userDetailsOption):

   • Entire flow is data‐driven: if visitorFields has 0 fields and passwordProtected is false, skip to file display.

Tasks

1. page.tsx: disclaimers, “Confirm” button → local state toggle or route to AccessPage.
2. AccessPage.tsx:
   • Integrate useDocumentAccess hook.
   • Show <AccessError> if invalid.
   • Direct‐access if no fields/password.
   • Else show <VisitorInfoModal>.
3. Validate everything works with the new JSON approach and name/email columns.
4. Ensure synergy with layout for consistent branding or help links.