Operator guideEN

Distribution Lists / Detail

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

How to use this guide

Start with the main guide

Follow the explanation and examples first. Extra definitions and formulas are available below when you need them.

What this page shows

This page shows one distribution list and a read-only table of the contacts currently attached to that list.

How operators use it

  • confirm the list name before it is used in a newsletter program
  • check how many contacts are currently attached
  • inspect the contact rows returned by the newsletter service
  • confirm whether the list needs to be reopened from the separate edit route

Route behavior that matters

  • The page title changes from the generic Distribution List shell to Distribution List: {name} after the detail payload loads.
  • This route reuses the same newsletter detail hook and contact payload as the edit page.
  • The contact table has no local search, filter, pagination, or row actions on this route.

Important caveats

  • The contact table is read-only on this page. No remove-contact action was verified on the current FE surface.
  • The page uses the distribution-list detail endpoint and trusts the contacts array returned with the list payload.
  • The shown contact count can come from contact_count on the list payload or from the current contacts array when that summary is missing.
  • The current FE detail page shows a back button only. It does not expose a local Edit action from this route.
More details

Definitions and formulas

Open only the section you need. The relevant section opens automatically when you request help for a specific item on screen.

Calculations3 topicsOpen details

Numeric route-id fetch gate

Logic
The FE parses `query.id` into a number before it calls the detail hook., `useGetDistributionList` passes `null` to SWR when the id is missing or not numeric, so the request does not run.

Contact-count fallback

Logic
The detail page prefers `list.contact_count` for the summary card., When the backend summary is missing, the FE falls back to `contacts.length`.

Shared detail and edit payload

Logic
The detail and edit routes both use `useGetDistributionList`., The read-only detail page therefore shows the same `contacts` array and summary payload shape as the edit route.
Columns6 topicsOpen details

ID

Internal contact record ID inside the newsletter service.

Visual Type
grid-column

Email

Recipient email stored in the list.

Visual Type
grid-column

First Name

Contact first name if the newsletter contact record has it.

Visual Type
grid-column

Last Name

Contact last name if the newsletter contact record has it.

Visual Type
grid-column

Phone

Phone number stored on the newsletter contact record.

Visual Type
grid-column

Tags

Tag list joined into one comma-separated string in the FE table.

Visual Type
grid-column
Caveats
Arrays are rendered as a comma-joined string.
More help

Related pages

Distribution Lists

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

Distribution Lists / Form

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

Email Newsletters / Distribution Lists

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

Activity Tag Rules / Detail

Rule inspection page with stored identity, conditions, timestamps, impact estimate, run action, delete action, and recent application history.

Affiliate Payment Settings / Detail

Detail/edit shell for one saved affiliate payment-setting record.

Affiliate Settings / Detail

Saved affiliate detail workspace for reviewing one affiliate and opening report actions.