Operator guideENcasinocrmcrudcatalog

Casino Catalog

Operator guide for casino-side game catalog administration, including games, categories, providers, sub-categories, aggregators, and ordering workflows.

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

Casino Catalog is the backoffice area used to maintain the casino-side content tree before operators move into NX-level mappings and restrictions.

Operators use this module to:

  • review master games and provider coverage
  • maintain visible game categories and sub-categories
  • edit provider records and blocked-country rules
  • reorder categories, sub-categories, and game lists
  • run maintenance actions such as disabling games or refreshing optimization lists

Surface map

  • Aggregators: casino-side aggregator registry with activation control
  • Banners: visual banner maintenance surface
  • Master Game: one master-catalog detail workspace
  • Categories: list, create/edit, and reorder for top-level casino categories
  • Games: main game list, edit form, reorder flow, disabling, and optimize tools
  • Providers: provider grid, edit form, and blocked-country relation page
  • Sub-categories: list, create/edit, reorder, and add-games relation flow

Where operators get confused

  • Casino catalog pages are not the same as NX mapping pages. Casino surfaces manage the source catalog; NX surfaces manage cross-market exposure and mappings.
  • Reorder screens change curated operator order. They are not the same thing as enabling or disabling a record.
  • Relation pages such as Add Games or Blocked Countries change where records can appear, even though they do not look like classic edit forms.

Verification scope

This module is currently documented as verified_fe_only baseline coverage:

  • FE routes, visible actions, filters, and grid structure are mapped from nx-admin-fe-workspace
  • backend mutation and read paths still need a full Cycle 2 verification pass
  • nx-workspace is not part of the current baseline unless an explicit shared dependency is found
Related references

Related pages

pageAffiliate Deals / Dashboard

Deal-period performance report that combines traffic, deposit, GGR, NGR, payout, and ROI metrics for affiliate deals.

pageAffiliate Deals / Form

Create and edit form for affiliate deals, including PID, date window, commercial terms, and responsible person.

pageAffiliate Deals / List

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

pageAffiliate Deals Overview

Operator guide for affiliate-deal records, their create/edit flow, and the performance dashboard that reconciles contract settings with delivered traffic and revenue metrics.

pageAutomatic Withdrawal / Detail

Management workspace for automatic withdrawal, combining the rules register with processed history and the non-qualified withdrawal queue.

pageAutomatic Withdrawal / Form

Create and edit form for one automatic-withdrawal rule, including thresholds, KYC, countries, methods, tags, and per-currency limits.