Skip to content

Settings — Legal

The Settings ▸ Legal page is the back-office surface where your organization’s administrators read and approve the legal acknowledgement documents that the platform presents at consent moments — terms & privacy, staff confidentiality handling, participant data & truth, biometric consent (with the Québec overlay), upload ownership & indemnity, e-sign consent, and matter representation consents.

It is admin-only. Approving a document is a deliberate, recorded act of legal sign-off — until it happens, the wording does not render live anywhere.

Each document carries a current wording in one of two review states:

  • Draft — pending review — the wording is seeded for attorney review and is never served live. This is the default for new copy.
  • Approved — a person with the legal-acknowledgements permission has signed off. The resolver then serves it live at its acceptance points, and every acceptance records the exact version the subject saw.

This is the same “Suggested — verify / attorney-review-pending” discipline used across the platform for any law- or regulation-derived value: nothing law-derived ships live without a human approving it against its cited authority.

Standard PageHeader with the title Legal Documents, a one-line description, and Settings breadcrumbs.

When any document is awaiting review, an amber banner summarizes the count and restates that those documents do not render live until approved.

Documents are grouped by kind. Each row shows the title, slug, kind, jurisdiction, current version, and a Draft — pending review (amber) or Approved (green) status badge.

Clicking a row expands:

  • The authority for any law-/regulation-derived clause — the citation and a View source link to the official text — so the reviewer can verify the copy against its source before approving.
  • The rendered legal copy (read-only). The text is sourced from the stored document body, never hard-coded into the app.
  • An Approve button (admins only) when the version is still a draft, plus the approver + approval date once approved.

Clicking Approve marks the version approved, records who approved it and when, and stamps an effective date so the resolver serves it immediately.

Approval is forward-only: there is no un-approve. A wording change is a new version to review and approve — the audit trail of who approved which exact text is never rewritten. Re-approving an already-approved version is a no-op that preserves the original sign-off.

RoleView draftsApprove
Owner / Admin
Manager / General

Approving legal copy is an organization-governance action; non-admins do not see drafts and cannot approve.