What this module is for

The Challenges module is the operator workspace for creating and maintaining challenge definitions, controlling who can receive them, and configuring automatic challenge generation.

Use it when you need to:

• create or edit a manual challenge
• review which challenges are active or closed
• close a challenge with a selected winner
• maintain challenge permission rules
• maintain automatic challenge generation configs

Surfaces in this module

• List: the main challenge catalog with status/source tabs and row actions.
• Form: create and edit flow for one challenge configuration.
• Detail: the challenge record in operator context, including close and winner-related behavior.
• Permissions: rule set controlling eligibility constraints for challenges.
• Auto Configs: generator rules that can create challenges automatically.

Where operators usually get confused

• Status and Active are related but not identical. The list can show a record as closed while the active checkbox is also false.
• Admin vs User source filters explain where the challenge originated.
• Closing a challenge is a winner action, not just a cosmetic status change.
• Permission rules and auto-generation configs are supporting surfaces. They do not behave like the main challenge list.

Verification scope

This module is documented from:

• FE routes, form sections, list actions, and supporting config pages in nx-admin-fe-workspace
• admin CRUD endpoints in gs-admin-backend
• casino-side challenge runtime only where it affects winner/state interpretation

nx-workspace is not part of the current verification path for these surfaces.