> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Policy Acknowledgment Forms

> Admin settings page for managing GR-owned forms that can be attached to a policy as its custom acknowledgment form, overriding the default attestation fields.

The Policy Acknowledgment Forms page (`/gr/settings/policy-acknowledgment-forms`) renders `PolicyAcknowledgmentFormsPage`, which lists `fw_forms` records owned by the GR core that are eligible to be attached to policies as acknowledgment forms.

## Overview

`PolicyAcknowledgmentFormsPage` calls `useEntityBreadcrumb` for navigation context and renders an informational `Alert` explaining the purpose of the page, followed by `ModuleFormsPage` filtered to `owning_core='gr'` with `moduleDisplayName='Policy Acknowledgment'`.

The alert reads: *"These forms can be attached to a policy as its acknowledgment form. When set, signers see the configured fields (instead of the default attestation) inside the acknowledgment dialog."*

New forms are created via `/fw/forms/new?core=gr&purpose=policy_acknowledgment`, subject to `FW_PERMISSIONS.FORMS_CREATE` (`fw.forms.create`).

## Who it's for

Requires permission: `gr.policies.acknowledgment-forms.manage` (`GR_PERMISSIONS.POLICIES_ACKNOWLEDGMENT_FORMS_MANAGE`). Users without this permission cannot access this route.

## Before you start

* You must hold `gr.policies.acknowledgment-forms.manage`.
* Forms created here appear as options in the policy detail page's acknowledgment form selector.
* Coordinate with legal or compliance before deploying a custom acknowledgment form.

## Steps

<Steps>
  <Step title="Open Policy Acknowledgment Forms settings">
    Navigate to `/gr/settings/policy-acknowledgment-forms`. The page lists all GR-owned acknowledgment forms.
  </Step>

  <Step title="Review existing forms">
    Browse the list of `fw_forms` scoped to `owning_core='gr'`. Existing forms can be opened for editing.
  </Step>

  <Step title="Create a new acknowledgment form">
    If you hold `fw.forms.create`, use the create action. You are directed to `/fw/forms/new?core=gr&purpose=policy_acknowledgment` in the Forms & Workflows module.
  </Step>

  <Step title="Attach a form to a policy">
    After creating the form, navigate to the relevant policy's detail page (`/gr/policies/:id`) and set the `acknowledgment_form_id` field to this form. The form will then appear to signers in the acknowledgment dialog.
  </Step>
</Steps>

## Key concepts

* **acknowledgment\_form\_id** — foreign key on `gr_policies` that links a policy to a specific `fw_forms` record, overriding the default attestation UI.
* **ModuleFormsPage (PF-08)** — shared platform component rendering a filtered, permission-aware forms list.
* **purpose=policy\_acknowledgment** — query parameter passed to the form builder to pre-configure the new form's intended use.

## Related

<Columns cols={2}>
  <Card title="Governance & Compliance" icon="scale-balanced" href="/gr/overview">
    Governance & Compliance core overview.
  </Card>

  <Card title="Governance & parity" icon="clipboard-check" href="/governance/index" />
</Columns>

<Note>
  This page documents shipped product behavior. It is not medical, legal, or
  billing advice. Verify against your organization's policies and applicable
  regulations before using it for clinical, compliance, or billing decisions.
  Protected health information (PHI) shown in the product is governed by your
  tenant's access controls and is never exposed in this documentation.
</Note>

<Accordion title="Documentation sources">
  * src/routes/gr.tsx
  * src/cores/gr/pages/settings/PolicyAcknowledgmentFormsPage.tsx
  * src/platform/permissions/constants.ts
  * src/platform/forms/ModuleFormsPage.tsx
</Accordion>