#Consent Notice (Compliance Copy)

#Overview

Consent Notice settings are managed from the Compliance Copy section in Settings at /settings?section=compliance-copy. The panel lets Client Admins manage customer-safe caller privacy and consent copy for one in-scope project at a time.

For Client Admins the Compliance Copy entry is intentionally hidden from the visible Settings sidebar, so open the section using the /settings?section=compliance-copy link. Client Managers see the entry in their Settings sidebar under Compliance and privacy and reach a read-only summary.

This customer settings panel does not provide a separate consent-notice version list, HTML editor, externally hosted notice URL, or Set as Active action. Instead, it shows the selected project's saved working copy, the currently published runtime copy, approved consent-template options when editing is available, preview text, provenance, and runtime publish status.

#Prerequisites

• You are signed in to the AiDial portal as a Client Admin to edit, or as a Client Manager to review a summary. See Signing In for instructions.
• Your session includes at least one in-scope project.
• Open /settings?section=compliance-copy directly. Client Admins do not have a Compliance Copy entry in the Settings sidebar; Client Managers reach the read-only summary from the Compliance Copy entry under Compliance and privacy.

#Access and Scope

The browser uses your portal session; you do not need to enter or send an API key. The browser calls the portal server, and the portal server forwards your bearer-authenticated request to aidial_api. Project access is resolved server-side from your authenticated session, and the browser sees only browser-safe project references.

Client Staff do not receive this Settings section. Client Managers see customer-safe rendered summaries only: a summary-only view shows the rendered collection notice and consent notice text, while the individual copy fields and the approved-template list are withheld. Client Admins can edit when the selected project is editable from the portal; some projects remain summary-only when the published runtime requires the partner-managed workflow. Navigation visibility is not the security boundary: the settings API route still enforces role and project scope for direct links, and only Client Admins are accepted for saves.

#Managing Consent Notice Copy

1. Open /settings?section=compliance-copy. Client Admins use this direct link because the entry is not shown in their Settings sidebar; Client Managers can also open Settings > Compliance and privacy > Compliance Copy for the read-only summary.
2. Choose the project you want to review. Client Admins use the project switcher in the portal sidebar; there is no project selector inside the panel for this role, and opening the section without a project in the address bar sends you to your most recently used project, or your first project. Summary-only roles use the Project selector inside the panel.
3. Review the project name, timezone, provenance, last changed time, runtime publish status, and published runtime observation time.
4. Choose an approved Consent template revision, if the panel is editable and the consent wording needs to change.
5. Optionally enter Optional custom consent text. This plain-text copy is appended after the selected approved template in the preview.
6. Review the collection notice and consent notice preview.
7. Select Save compliance copy.

Screenshot reference: Compliance Copy panel with project selector and runtime status

Screenshot reference: Compliance Copy consent template and preview fields

Saving stores the project-scoped working copy. The Runtime publish status indicates whether the saved working copy already matches the published runtime, is pending publish, or is not publish-ready. Do not treat a saved change as active for callers until the published runtime status confirms it.

#Field Reference

#Runtime State and History

The customer-facing panel does not expose a separate Create Version, Publish, Restore as Draft, or Set as Active action. Its only controls are Save compliance copy, Reset changes, and Reload latest, plus a Retry compliance copy button that replaces the panel if the section fails to load. Backend revision tracking records saved working-copy changes, while the portal displays the current primary projection, published runtime projection, and saved working projection when available. Moving the saved copy into the published runtime uses the partner-managed publish workflow.

The panel may show:

• Published runtime matches — the saved working copy matches the published runtime.
• Pending publish — the saved working copy differs from the runtime copy and still needs the partner-managed publish workflow.
• Not publish-ready — the runtime state, approved template registry, or pinned template revision needs attention before it can be published safely.

#Empty and Summary States

• No in-scope projects available — your current session does not include an active project that can show compliance copy.
• Choose a project to continue — more than one project is in scope; select one before reviewing copy details. This applies to summary-only roles, because Client Admins are scoped to a single project automatically.
• Compliance copy is not provisioned for this project — the project is assigned to your account, but customer-safe privacy and consent copy is not connected yet. Contact support or choose another in-scope project.
• Summary only — your role or the selected project's runtime state allows review, but not editing.
• Managed elsewhere — the current published runtime cannot be edited safely from the portal panel; contact your delivery partner for changes.

#Common Issues

#Related Pages

• Settings Overview
• Collection Notice
• Tenant Settings