Operator surface for deciding which registration fields are required in the global registration profile.
Follow the explanation and examples first. Extra definitions and formulas are available below when you need them.
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.
optional and required. It does not expose a separate hidden state.Single-surface grid for reviewing the registration field set and saving required-field changes.
Operator guide for choosing and ordering which active, published CMS banners appear in the registration modal.
Selection and ordering screen for registration-modal banners, with per-banner edit, reorder, and remove controls and a single save.
Operator workspace for reviewing the merchant-balance transaction journal and creating manual debit or credit adjustments.
Operator documentation for activity-driven tag automation rules, including list, create, edit, detail inspection, and recent application history.
Read-only recent recorded application rows inside rule detail, including user ID, tag outcome, timestamp, and captured activity payload.