Operator guideENnewsletterdistribution-listsrecipients

Distribution Lists

Operator documentation for newsletter recipient lists, including detail, rename, contacts inspection, and CSV upload or attach flows.

Reader view

Clean portal guidance

This page keeps the operator explanation, field and action descriptions, and screenshots visible without exposing repo paths, raw sidecars, or editorial-only implementation details.

Narrative content

Page body

What this module is for

Use Distribution Lists to manage reusable recipient lists for newsletter programs.

Operators use this area to:

  • inspect one list and its current contacts
  • rename an existing list
  • upload a CSV file and attach contacts to an existing list
  • upload a CSV file and let the system create a new list automatically

Main surfaces

  • Distribution Lists / Detail shows one list and the contacts currently attached to it.
  • Distribution Lists / Form documents the rename flow and the implicit create-on-upload branch.
  • Distribution Lists / Contacts explains the read-only contacts grid shown on detail and edit pages.
  • Distribution Lists / Upload Flow explains the CSV preview, file upload, new-list creation, and add-contacts chain used from the newsletter tab.

Important caveats

  • There is no standalone backoffice list route for distribution lists. Operators reach the main inventory through Email Newsletters on the Distribution Lists tab.
  • The standalone routes that exist today are only:
    • /distribution-lists/[id]
    • /distribution-lists/edit/[id]
  • Newsletter list operations do not go through direct gs-admin-backend CRUD ownership. The FE calls /api/newsletter/*, the proxy resolves core settings, and then forwards the request to nx-newsletter-service.
  • A new list can be created without a dedicated create page. If the upload card has no target list selected, the FE first creates a list and then attaches parsed contacts to it.

Verified ownership

  • FE routes, columns, buttons, and standalone pages: nx-admin-fe-workspace
  • proxy and forwarding contract: apps/backoffice/pages/api/newsletter/[...path].ts
  • required core settings for the proxy:
    • newsletterURL
    • newsletterMerchantKey
  • downstream CRUD and file endpoints: nx-newsletter-service HTTP contract

Verification status

  • status: verified_backend_and_core
  • verified path:
    • FE routes and hooks in nx-admin-fe-workspace
    • newsletter proxy in backoffice
    • core settings lookup for newsletter endpoint and merchant key
    • downstream nx-newsletter-service routes for list read, list update, list create, file preview, file upload, and add-contacts
Related references

Related pages

pageDistribution Lists / Detail

Read-only detail workspace for one distribution list and the contacts currently attached to it.

pageDistribution Lists / Form

Rename flow for an existing distribution list plus the implicit create-a-list branch triggered from the CSV upload card.

pageEmail Newsletters / Distribution Lists

Reusable contact-list inventory with CSV preview, upload, create, and add-contacts actions.

pageDistribution Lists / Contacts

Read-only contact grid attached to one newsletter distribution list.

pageDistribution Lists / Upload Flow

CSV preview and upload flow used to validate files, create a target list when needed, and attach contacts.

pageEmail Newsletters

Operator workspace for newsletter campaigns, distribution lists, and send-log review through the backoffice newsletter proxy.