Operator guideENsignupregistration

Signup Fields

Operator surface for deciding which registration fields are required in the global registration profile.

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 Signup Fields to control which registration fields are required at the global product level.

The current CRM surface is a single table with a required toggle for each supported field and one submit action that saves the whole configuration.

Important caveats

  • Some fields are strictly required and cannot be changed on this surface.
  • The current UI only toggles between optional and required. It does not expose a separate hidden state.
  • The saved values are stored as the global registration configuration in gs-admin-backend.
Related references

Related pages

pageSignup Fields / Detail

Single-surface grid for reviewing the registration field set and saving required-field changes.

pageCMS / Registration Banners

Operator guide for choosing and ordering which active, published CMS banners appear in the registration modal.

pageCMS / Registration Banners / Detail

Selection and ordering screen for registration-modal banners, with per-banner edit, reorder, and remove controls and a single save.

pageActivity Tag Rules

Operator documentation for activity-driven tag automation rules, including list, create, edit, detail inspection, and recent application history.

pageActivity Tag Rules / Applications

Recent application history shown inside the detail page for one rule, including action performed, timestamp, and captured activity data.

pageActivity Tag Rules / Create

Create flow for a new activity tag rule, including optional clone-from-existing behavior and condition testing.