#Consent Notice (Compliance Copy)

#Overview

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

The portal 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, 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.

#Access and Scope

The browser uses your portal session; you do not need to enter or send an API key. Project choices are limited to your current scope.

Client Staff do not receive this Settings section. Client Managers see customer-safe rendered summaries only. 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.

#Managing Consent Notice Copy

1. Navigate to Settings > Compliance Copy.
2. If more than one project is available, choose the project you want to review.
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. 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.

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.
• 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