Glossary

Below is a glossary of common terms you will find in the hizi-app. It also explains how we define each term.

• Account (Commercial Account): groups Partners or Identities that are commercially connected, for CRM purposes. This was the field "Account" in the previous backoffice. You found it in the "operator" record, now known as Identity.
• Audit: the change-history trail of who created, updated, or deleted what, and when. This did not exist as a viewable section in the previous backoffice.
• Billing Group: bundles several Identities under one Legal Entity for combined invoicing (still a work-in-progress feature). This was known as "Group" in the previous hizi backoffice.
• Docker Registry: your connected GitLab-based Docker registry. It is the source for synced repositories and images.
• Docker Repository / Docker Image: the synced repository and image-tag list under a registry. An Image is what a Game's Docker version points to.
• Freeplay: a promotional free spin grant to a player for a specific game.
• Game: a catalogue entry with a code, an Origin, and a status. Only Published games go live.
• Game Launcher: a tool to test-launch a game (with a real or test player, a demo, or a shareable demo link).
• Gameround: one played round of a game. You can search for it by hash or by filters, with a full detail and forensic view. This is more powerful than the "Game round lookup" from the previous backoffice.
• Game Studio (also known as Brand): the publisher entity that owns Games and sits between the tenant and its Games. This was known as "Game provider" in the previous hizi backoffice.
• Geo Rule: a named allow or deny list of countries and IPs. You can attach it to a Partner, Game Studio, Identity, or Game.
• Hizi Engine Config: a saved build or config from the hizi engine's own creator tool, attached to a Game.
• Identity: a specific operator brand or casino site under a Partner. Games are access-controlled per Identity. This was known as an "Operator" in the previous hizi backoffice. Why is it now called an Identity? One "operator" might have several brands linked on their side. Each brand has its own Identity, for more clarity.
• Identity Settings / Identity Game Settings templates: reusable, live-linked presets applied to one or more Identities. In the previous backoffice, you found this in the "Operator" details, in the field known as "custom settings". That field used JSON only. Now you configure the settings with toggles.
• Legal Entity: the company record (name, address, VAT) required for invoicing.
• Logs: game transaction and communication details. You use them for debugging.
• Origin: the way you build a Game: with the hizi engine, a Docker image, or RGS-to-RGS (your own infrastructure).
• Partner: the top-level business relationship with a casino operator group. It is the parent of Identities and Legal Entities. The old hizi backoffice did not clearly define this concept. The Partner name usually appeared under "Operator Group", so you can consider it similar to that.
• Player: a per-tenant wallet record (balance, currency) linked to gamerounds and transactions. This is the same functionality as the "Player" section in the previous backoffice. You use it primarily for testing.
• Publish: the "go live" action that pushes your published games, versions, and permissions out to the operator sites. Everything before this step is a draft.
• Site: a deployed regional server (production or staging) that an Identity runs on. This did not exist in the previous hizi backoffice. Each site instance had a separate log-in.
• Stats: the historical KPI dashboard (revenue, rounds, players) pulled live per site. This is the "Statistics" section from the previous backoffice.
• Transaction: a single wallet debit or credit entry in the ledger.
• Users: Hizi app users, not end users. Configure accounts for hizi app users here, including roles and permissions. This was labelled as "Logins" in the old backoffice.
• Wallet test runner: a simulator to run wallet-API test cases against an Identity before you go live. The previous backoffice called this the "Operator integration test suit".