Operator guideEN

Image Gallery / List

Standalone email-gallery page with drag-and-drop upload, thumbnail preview, delete confirmation, protected storage updates, and automatic gallery refresh after upload or removal.

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 surface does

This is the verified page for the reusable email image gallery.

Operators use it to upload images that can be reused by email/template workflows, review the returned thumbnail set, and remove an image when it should no longer stay available.

How the page is organized

  • the upload dropzone sits above the gallery
  • the gallery renders one thumbnail card per returned image
  • each thumbnail exposes one delete control
  • deletion is guarded by a confirmation dialog

How to read the page

  • each tile represents one stored gallery image
  • the image preview is rendered from the stored image URL
  • the image name is the uploaded file name recorded with the gallery entry
  • the delete button opens a confirmation step before removal

Main actions

  • upload one or more images through the dropzone
  • open delete confirmation for one gallery image
  • confirm deletion for the selected image

What happens after an upload

When an upload succeeds, the file is stored by the backend, the gallery setting is updated with a new image record, and the visible gallery refreshes. The gallery record keeps the uploaded file name and the generated image URL.

What happens after a delete

When deletion succeeds, the backend removes the stored file referenced by that image URL, rewrites the gallery setting without that image, and the visible gallery refreshes. The delete action is permanent for this gallery entry; there is no undo action on this page.

Known caveats

  • The page does not show rich metadata beyond the returned image itself.
  • The gallery is available for superadmin-style gallery storage. If the backend does not treat the current operator as an eligible gallery owner, the returned gallery can be empty and mutations may not produce a visible item.
  • The upload UI can accept multiple dropped files, but the current backend request handler processes a single uploaded file field per request. Operators should verify the refreshed gallery after multi-file drops instead of assuming every selected file was persisted.
  • There is no verified FE action to edit captions, rename an image, or reorder gallery items on this route.
  • Upload and delete are tracked as configuration audit events.
More help

Related pages

Activity Tag Rules / List

Main inventory for activity-driven tag rules, with search, activity and status filters, grouped rows, clone, edit, and run actions.

Affiliate Deals / List

Searchable table of affiliate deal rows with PID filter, create action, dashboard shortcut, and edit/delete row actions.

Affiliate Payment Settings / List

Affiliate payment settings inventory page for reviewing configured rows and opening saved records.

Affiliate Settings / List

Affiliate inventory list used to review saved affiliates and open detail or report flows.

Auto Tags Manager / List

Rule inventory with search, direct navigation to create or reorder, row-level run controls, and job history or recovery actions.

Automatic Withdrawal / List

Rule register for automatic-withdrawal logic, with search, status filtering, row actions, and create navigation.