Your first week

An order of learning that avoids the usual early mistakes.

Day one — look, do not change

Log into the admin panel on staging and find your way around. Open a player, read their wallet and transaction history, open the bonus list, run a report. Do not create anything yet.

The most useful habit to build early: whenever something does not behave as you expect, check whether you are looking at a definition (a rule you configured) or an instance (what a specific player actually received). They look similar and are not the same thing. Bonuses / How bonuses work explains the distinction in the context where it matters most.

Day two — make a player and pay them

On staging, register a player from the player site, then credit them from the admin panel. Watch what happens in the player's wallet and history.

This single exercise teaches you more than any amount of reading: you will see the difference between a real deposit, a correction and a bonus credit, and why choosing the wrong one quietly changes your reporting. See Payments / Crediting a player.

Day three — build a campaign

Create a bonus campaign on staging, trigger it with a deposit, and follow it through to the point where the player can use the money. Then deliberately break it: change the currency, expire the date, pick a payment method the panel cannot send. Watching a campaign fail teaches you what to check when a real one does.

Bonuses / Building a campaign walks through this.

Day four — learn where the truth is

Reports, the player's transaction history and the bonus wallet each answer different questions. Learn which one to trust for which question before you need it during an incident.

Before you touch production

• Know which brand and which environment you are in. The panels look identical.
• Know who to tell. Bonus and payment changes affect real balances immediately.
• Assume anything you configure will be seen by a player within minutes.