LINKUWANT COMMUNICATION CONFIGURATION
=====================================

STATUS:
DOCUMENTATION ONLY — NOT IMPLEMENTED


PURPOSE
-------

The future common communications generator will require configuration.

Configuration should be centralized rather than hard-coded into individual
forms or communication templates.


FUTURE CONFIGURATION MAY DEFINE
-------------------------------

FORM / COMMUNICATION TYPE
    - Form name
    - Form directory
    - Database table
    - Database field prefix

TEMPLATES
    - User email template
    - Administrator email template
    - Response templates
    - SMS/Text templates

RECIPIENTS
    - Administrator recipient(s)
    - Multiple administrator recipients
    - CC
    - BCC

SENDER INFORMATION
    - From
    - Reply-To

EMAIL
    - Subject
    - Header
    - Footer

REPLACEMENT FIELDS
    - Common field mappings
    - Form-specific field mappings
    - Generated fields

ACTIONS
    - Available administrator actions
    - Required permissions
    - Expiration rules
    - Confirmation requirements

LOGGING
    - Communication type
    - Recipient
    - Template
    - Delivery result


IMPORTANT
---------

Do NOT put passwords, API keys, database credentials, SMTP passwords, or
other secrets in communication templates.

Actual secret storage/configuration will be designed separately.