Documentação

English

Português
Español

English

Português
Español

Appearance

Newsletter ​

Access Prerequisites

  • Permission (module): access granted by the administrative route guard (admin). The route is /users/newsletter, but the item appears in the Communication group. (In the master-map the permission is listed as admin/viewUsers — VERIFY in your environment.)
  • License/Feature: None.
  • Menu container: GENERAL → Communication group (icon campaign) → Newsletter.

What it is / when to use ​

Lists the e-mail addresses of users subscribed to the platform newsletter. This is a query and export screen — it does not create or send any communication. Use it to audit the subscriber base and export the list (CSV) for use in campaign tools or to feed a send via Email sending.

Prerequisites ​

  • Permission: item under administrative route guard. Permission in Axia is dual (CPM enum + dynamic module in the DB).
  • License/Feature: none.
  • Dependencies on other screens: the subscription itself is performed by the end user (Midas-Web); here you only query the result.

Step by step ​

  1. Open the Communication → Newsletter menu.
  2. The screen loads the list of subscribed e-mails (sorted alphabetically).
  3. Use the search field to filter by a substring of the e-mail address.
  4. Click Export to download the list as a CSV file.

Fields / Columns ​

Filter/ColumnWhat it showsData source
SearchFilters the list by e-mail substring (case-insensitive)client-side filter over the loaded list
E-mail (column)E-mail of each subscribergetAllUserNewsletter (UserRolesService → CPM)

Actions and modals ​

  • Export (CSV): generates a newsletter_<date>.csv file (with UTF-8 BOM) containing the list of e-mail addresses. The CSV header includes the columns email;name — the name column may be empty when the backend returns only the e-mail. The download is client-side (does not call the backend).

Business rules / considerations ​

Attention

  • Read-only screen — there is no creation, editing, or sending here. To send to the subscriber base, use Email sending.
  • The list reflects who opted in to receive the newsletter (user opt-in). Treat the CSV as personal data (LGPD): control who exports it and where the list is used.
  • There is no actual send pagination here; this is only the subscriber base.