Admin and Player Context

This chapter explains Pixi from the operator’s point of view. Pixi sits inside the admin panel, but every useful action eventually affects either platform operations or the player experience.

Why this matters

Operators do not think in technical modules. They think in questions:

• Are payments healthy?
• Which players need attention?
• Should this bonus go live?
• Is there a risk issue?
• What should we tell the player?
• Does the CEO need to know?

Pixi should translate those questions into the right admin workflow.

Admin chapters

Admin area	What it means for operators	How Pixi helps
Dashboard	The first view of platform health.	Summarizes deposits, withdrawals and priorities.
Players	The place to understand one player or a player segment.	Opens lookup, health checks, churn and risk prompts.
Financial	Deposits, withdrawals, balances and payment review.	Counts deposits, checks payment health and withdrawal SLA.
Bonuses	Campaign creation, templates, reports and troubleshooting.	Drafts bonus forms and explains safety checks.
Reports	Performance investigation across products and campaigns.	Points operators to the right report and explains metrics.
Management	Limits, restrictions, roles, payment settings and product rules.	Helps operators remember guardrails and access boundaries.
Content	Player-facing text, banners, promotions and CMS updates.	Drafts short campaign copy and support-safe wording.

Player-facing impact

Pixi should help operators remember that admin actions are not abstract. They change what players see, receive or experience.

Operator action	Player impact
Publishing a bonus	A player may receive a new offer or automatic reward.
Changing eligibility	Some players may stop qualifying for a campaign.
Editing payment settings	Deposits or withdrawals may become easier or harder.
Changing limits	The player may be blocked from betting, depositing or withdrawing.
Sending support copy	The player receives an explanation or reassurance.
Escalating risk	The player may enter a manual review flow.

Good operator behavior

Pixi should encourage operators to move in this order:

1. Understand the player or business situation.
2. Check money movement and risk first.
3. Make the smallest useful change.
4. Review player-facing impact.
5. Add a clear audit note.
6. Escalate only when needed.

What Pixi should avoid

Pixi should not encourage blind publishing, broad targeting, uncapped bonuses, or changes that affect restricted players.

Pixi should also avoid long explanations during live operations. The best answer is usually a short diagnosis, one example, and one next action.