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
• review closed/winner state where a challenge already has winner data
• maintain challenge permission rules
• maintain automatic challenge generation configs

Surfaces in this module

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

Where operators usually get confused

• Status and Enabled are related but not identical. The list can show a row as Won while the enabled flag is false.
• Admin vs User source filters explain where the challenge originated. User means the admin owner field is empty (adminUserId IS NULL), not that the row belongs to the currently opened player.
• Closing a challenge is a winner-state action, not a cosmetic status change; the current interface does not render that close action directly on the detail page.
• Permission rules and auto-generation configs are supporting surfaces. They do not behave like the main challenge list.

Known caveats

• Supporting pages such as Permissions and Auto Configs define reusable rules. They do not create active challenge instances by themselves.
• Some helper selectors, such as game, asset, language, and translation data, come from shared platform catalogs. Saving a challenge still depends on the challenge form itself.