Navigating to Configuration

  1. In the left navigation, expand Governance Hub and click Configuration.
  2. Select the connection you want to configure from the connection selector at the top.

The Configuration page has two areas: the check list and the settings drawer.

Browsing the Check Catalog

The check catalog shows all available checks organized by category. Each check displays its name, type (automated or semi-automated), and current enabled/disabled state for your connection.

Categories include:

  • Program Setup — token presence, token values, campaign dates, exclusion lists, contact thresholds, opt-out filters, suppression lists
  • Email Settings — naming conventions, sender validation, subject line length, preheader length, view as web page
  • Email Content — link validation, unsubscribe presence, header/footer structure, mailto links, social icon URLs
  • Smart List — email selection, setup tab fields, smart campaign config, filter error review

New checks are added to the catalog over time. New checks appear as disabled by default — they will not affect existing QA runs until an admin enables them.

Enabling and Disabling Checks

  1. Find the check you want to enable in the catalog.
  2. Click the toggle to enable or disable it.
  3. When enabling a check, you can set:
    • Required or Optional — Required checks must have a result before self-review can be submitted. Optional checks appear in QA runs but do not block the workflow.
    • Severity — Error, Warning, or Info. This controls how the result is displayed. Changing severity does not affect whether the check blocks self-review (only the Required flag does).

Important: Disabling a check while a QA run is in progress does not affect that run. The change applies to the next run started after the change.

Configuring Check Parameters

Some checks have configurable parameters — thresholds, patterns, or allowed values that control what the check validates against.

  1. Click the settings icon (gear) next to an enabled check.
  2. In the configuration dialog, set the parameters for your connection.
  3. Click Save.

Common configurations:

  • Subject line length — Set the maximum character count (default: 50)
  • Preheader length — Set the maximum character count (default: 90)
  • Token presence — Define the list of required token names (e.g., Campaign Market, UTM Source, End Date)
  • Token value validation — Define allowed values for specific tokens (e.g., utm_source must be one of: google, linkedin, facebook)
  • Naming convention — Define a regex pattern, description, and example for email asset naming
  • Sender validation — Set expected From Name, From Address, and Reply-To Address
  • Suppression list — Set the expected suppression list name(s) (default: Master Suppression List)
  • Contact count threshold — Set the minimum audience size (default: 100)
  • Link validation — Configure redirect following, max redirects, and timeout

Tip: If you leave all configuration at defaults, checks run with sensible platform defaults. Configuration is for customization, not required for setup.

Important: Every parameter change is versioned. When a QA run starts, the engine captures a snapshot of the configuration. Historical QA results always reflect the rules that were active at the time of the run, not the current configuration.

Creating Custom Manual Checks

Admins can create custom checks for org-specific process steps that are not covered by the built-in catalog.

  1. Click Add Custom Check at the bottom of the check list.
  2. Fill in the following fields:
    • Name (required) — A descriptive name for the check
    • Description — What the check is for
    • Instructions — Step-by-step guidance for the person completing the check
    • Category — Select from existing categories or custom categories
    • Severity — Error, Warning, or Info
    • Required — Whether this check blocks self-review
  3. Click Save.

Custom checks appear alongside catalog checks in QA runs. Users see the instructions and must manually mark the check as Pass or Fail with optional notes.

Limits: A maximum of 50 custom checks can be created per connection. If more are needed, contact support.

Editing and deleting: Editing a custom check updates it for future runs only. In-progress runs retain the version at time of run start. Deleting a custom check excludes it from future runs but preserves it in historical results.

QA Settings

Click the settings icon (gear) in the top-right of the Configuration page to open the settings drawer.

Key settings include:

  • Peer review required — Toggle on/off. When enabled, QA runs require a second reviewer to approve or flag issues before the run is marked complete. When disabled, self-review completes the run.
  • Custom categories — Define additional categories for organizing custom checks.

These settings control how strictly the QA workflow is enforced across your org.