What this module is for

Referrals is a low-frequency operator screen used to review users who are linked to a referrer and to jump quickly into the related player profiles.

It is not a separate referral-program editor. The page is a referral-focused view of the shared player list.

Surface map

• List: the only route-owned surface in this module. It shows referred users with shared player filters, a referral-specific Referrer column, CSV export, and profile links.
• Related workflow outside this route: custom referral link and stream text editing live under Player / Referral Stats, not on /referrals.

When operators usually open this module

• a support or affiliate question needs the referred user list
• an operator needs to identify the parent referrer behind a player
• a team member needs to jump from a referred user into the referrer or the referred player profile
• a CSV export of the current referred-user slice is needed

Important caveats

• The page reads the shared /api/admin/get-users endpoint with isReferrals=true. It is not backed by a dedicated referrals CRUD service.
• Date start and Date end filter player creation dates because the underlying user list filters users.created_at, not referral-link creation timestamps.
• Last Deposit Date uses nx.user_kpi_summary, so it is a player KPI filter layered onto the referral subset.
• Search ClickID or PID switches the backend into a dedicated affiliate-link SQL path. In that path, the referral subset filter is not applied, so the result set behaves like affiliate-link search rather than strict referral-only filtering.
• Editing referral copy such as Custom Referral Link or Stream Custom Text is a related player-detail workflow and should not be documented as part of the /referrals page itself.