Management

The management area configures what the casino module knows about: game names, entities, entity groups and tips.

Game names

Games are named here, and those names appear on every rating, session and analytic the module produces.

Use the names your floor actually uses. A game called by one name on the floor and another in eConnect makes every report need translating, and it is exactly the kind of mismatch that survives for years because nobody owns it.

Entities

Entities are tables, gaming devices and the other things activity refers to. Add a gaming device, edit its details, and enable or disable it.

Disable rather than delete a decommissioned table. Its historical activity stays attributable, where deleting the entity degrades every past record referring to it.

Working with a large floor

The entity pages are built for estates with thousands of rows: the lists page, filter and sort server-side rather than loading everything into the browser, so a property with four thousand devices behaves like one with forty.

Entity groups

Entities can be grouped — tables into pits, pits into areas. Groups do two jobs:

• They are the natural unit for aggregation: comparing four pits is more useful than comparing forty tables.
• They are what logical groups select on, so a group is how "this supervisor sees the high-limit area" is expressed.

Selecting a group in a logical group also covers tables added to it later, where selecting individual tables does not.

Entity attributes

Entities carry attributes describing their configuration — limits, game type, and other properties the module uses when interpreting activity.

Keep them current. Analytics interpret activity through these attributes, so a table whose recorded limits no longer match reality produces figures that look wrong for reasons nobody can find.

Tips

Blackjack tips are configured here, feeding the module's handling of gratuities in its calculations.

Permissions

Management functions have their own permission keys, separate from viewing casino data. Somebody can work with ratings and sessions all day without being able to change what a table is — which is normally the right arrangement. See Permission Groups.

Keeping it current

Casino configuration goes stale when the floor changes: a table moved, a game changed, limits adjusted. Review after any physical change, and check that associations to cameras still point at the right tables.

What is recorded

Management changes are audited under the administration types, so a configuration change that makes historical figures confusing can be traced. See Reading the Audit Trail.