Configure a notice and its recipients

Purpose

Administrators choose a notice purpose, audience settings and the message template reused by billing work.

How It Works

Administrators choose a notice purpose, audience settings and the message template reused by billing work. Direct-recipient notices require an empty role list, while role-recipient notices require one to fifty distinct roles and reject invalid combinations with a field explanation. Notices default to the billing-notice purpose and reject any purpose outside that sole supported choice, listing the available purpose. A notice selects the communications template it sends, cannot send without that selection, and loses the selection when a replacement omits it. Message content belongs to the communications template rather than the billing notice. A send-notice reference from any template prevents notice deletion, including references from inactive templates, with up to twenty dependent templates named. An installment-only notice reference does not prevent deletion, leaving subsequent work blocked by the missing notice. Notice names remain unique within the workspace, and whole-record replacement refuses a version older than the current notice. Notice readers may inspect configuration, while creation, replacement and deletion require administrator permissions. The console has no communications-template selector and disables the message designer, so notices created there require template selection elsewhere before sending. The product should expose the published-template choice in the notice editor. Configuration locks can also refuse changes or deletion.

Relationships

Templates reference configured notices. During execution, notice sending uses their recipient and message settings.