Game permissions and default settings

https://environment.hoelle.games/gamespermissions

(please exchange environment with either dev, staging or europe-1)

Starting with version V1.9 of the hinterzimmer back office, game permissions can be set using this page (admin rights necessary)

Game Permissions can be used to allow / disallow games per operator / country and currency. Policies have to be entered as a valid JSON object (you can use jsonlint.com to validate JSON objects).

Above is an example of the default policy which allows all operators / countries / currencies to launch the game.

Game permission configuration history on production should be recorded in the internal production tracking spreadsheet.

---

Structure of game permission JSON object

A game permission can contain any of the following lists, each list consisting of an array of strings containing operator ids, 2 letter ISO country codes or 3(4) letter currency codes.

Allow lists are evaluated before deny lists, meaning if entries in an allow list exist all other operators will be denied.

Operator lists are evaluated before country code lists and before currency code lists.

{
        "operatorIdAllowList": [],
        "operatorIdDenyList": [],
        "countryCodeAllowList": [],
        "countryCodeDenyList": [],
        "currencyCodeAllowList": [],
        "currencyCodeDenyList": []
}

Following is an example of combining an operator allow list with a currency deny list

{
  "operatorIdAllowList": [
    "internal_testoperator"
  ],
  "currencyCodeDenyList": [
    "USD",
    "UBTC"
  ]
}

Following is an example of an operator allow list with two operator IDs. Both of these operators will be able to launch the game in question. Any other operator will be blocked. This could be used in the case of custom games etc. for a particular operator.

{
    "operatorIdAllowList":
["31829bfdcc1d40f8ab77a1c2938adf14",
"91fc92e9ea14463d9a3aa8864660de07"]
}

In addition to that forced gamesettings can be defined which will override all other settings done via operator config or profiles.

globalGameSettings / forced can contain any valid gamesettings

The following example disables the gamble feature for the specific games, combined with an operator deny list.

{
  "globalGameSettings": {
    "forced": {
      "gambleEnabled": false
    }
  },
  "operatorIdDenyList": [
    "c72f7ccb80614251ad86e1da29aa230b",
    "3b4e392a7c29434c99190a6618b93cc0",
    "93d63d55b45d47939344683d9d522897",
    "b9c1abc13b1447cb9242c2b3e1e0e335"
  ]
}