Getting Started
First-day checklist for your team in the Phoenix Prediction back office
Use this page when your team opens the Phoenix Prediction back office for the first time.
The goal is not to publish many events on day one. It is to set up your team, check what your players will see, and publish only events your team can confidently settle.
Sign in and invite your team
Phoenix invites your first Admin by email. The Admin then invites everyone else under Manage > Team & roles and gives each person a role: Admin, Content, Support, Finance or Viewer. See Staff and Roles.
Give each person the narrowest role that lets them do their job.
Check your environment
The header shows which environment you are working in: Production or Sandbox (Sandbox also shows a band across the page). Curation, trades and money are kept per environment; your events, categories, players and operator settings are shared by both.
Before changing what players see, check the environment selector.
Learn the main areas
| Area | What it is for |
|---|---|
| Dashboard | Volume, revenue (GGR), active players, orders and open interest, and where your markets are |
| Queue | What needs a person now: results on your own events, holds, and Scout's suggested questions |
| Events | Every event your players can see, platform and your own; your categories; the translations of your events |
| Curation | What your players see first, and which events they see at all |
| Scout | What Scout looks for, and its history (when Phoenix has set Scout up for you) |
| Trades | Every player action, with the wallet moves it caused |
| Finance | Daily reconciliation and every wallet move |
| Players | Find a player and read their positions, trades and money; block or unblock them |
| Manage | Your operator's settings, each environment's setup, and your team |
Which areas each person sees depends on their role. See Back Office Basics.
Check your settings
Your Admin opens Manage > Your operator and checks the display name players see, your languages and formatting country, and, for the environment the header shows, each currency's minimum and maximum order (sandbox and production keep their own). The Go-live tab lists what is still open for each environment. Fees, the trading engine and your currencies are set by Phoenix.
Check what players see
Open your site's embed and check, as a visitor and as a signed-in player:
- Your name or logo, colors and language are right. Your Admin sets the look under Manage > Your operator > Appearance (see Your Look).
- If you offer more than one language, open an event in each language on its language bar. A text that shows in the original language there has no approved translation yet, and your players read it the same way (see Languages and Translations).
- The bet slip's quick-amount buttons and price format suit your players, and your safer-gambling message and links show. Your Admin sets them under Betting and Player protection, beside Appearance (see Betting Settings and Player Protection).
- The category bar and the first events are the ones you expect. If not, adjust them in Curation.
- Buying, depositing and signing in work from the embed.
- The layout works on a phone.
Publish one event of your own
Start with one simple Yes/No event that you can settle from a public source. Your events have no environment of their own: once published, an event is visible in sandbox and production alike, unless you hide it in one environment's Curation. See Your Events and Results.
Use it to confirm:
- The title, question and outcomes are clear.
- The event appears in the expected category for your players.
- Trading closes at the expected time.
- The rules are specific enough for support.
- After closing, the market appears in your Queue and you can enter its result.
Establish a daily routine
At minimum, someone should check every day:
- Queue > All: results due on your own events, holds to review, and Scout's suggestions.
- Queue > Coming up: markets closing in the next hours.
- Dashboard: volume, suspended books, and markets on hold.
- Trades: any payout shown as Refused, which means your wallet refused it (see Settlement).
Know when to escalate to Phoenix
- Players cannot place orders, or many orders are rejected.
- A payout shows as Refused and you have fixed the cause on your side.
- A platform event looks wrong, or its result does.
- A market cannot be settled fairly from its published rules.
- Someone on your team cannot get access they need.