InkPlayUse a small test group before installing every station.
Operations and support
Deployment evidence
Onboard InkPlay without gambling the whole gaming floor.
InkPlay documents a pilot-first deployment path: prepare the owner and branch, install Controller on a stable staff machine, activate the branch, validate one or two Agent PCs, then expand after the complete session loop works.
Owner website access and local staff access are separate flows.
Start, extend, transfer, stop, and review a session before rollout.
Stage 1
Prepare ownership and the real branch identity.
The first account should stay under business control, and the first branch should match the venue staff actually operate.
- Create the owner account with a business-controlled email and retain recovery access.
- Create the branch with its real name, location, contact context, and intended PC or console modules.
- Choose a stable counter or staff workstation that remains powered during operating hours.
Stage 2
Install Controller, then activate the correct branch.
Controller and the Local Node establish the branch operating context before staff or player PCs are added.
- Use the current official Controller installer from the owner download area.
- Confirm the Controller shows activation, staff login, or dashboard readiness instead of a blank state.
- Create individual staff access with only the permissions needed for the role.
Stage 3
Prove the real workflow on one or two Agent PCs.
A small test group makes network, launcher, policy, session, and staff issues observable before they affect the floor.
- Install Agent on one or two PCs and confirm each device appears online and under the correct branch.
- Run a guest or player session, then test extend, transfer, stop, and session history.
- Open the games and launchers the venue actually uses after any policy or shell change.
Stage 4
Train staff, capture recovery context, and expand deliberately.
The floor should grow only after staff can operate the tested workflow and owners know how to recover or escalate.
- Train staff using the same language and permissions they will use during live shifts.
- Record installer versions, backup status, recovery ownership, and the escalation contact.
- Expand in manageable groups and recheck device health after each group.
Helpful guides
Continue with the operator manuals.
Common questions
Onboarding questions, answered clearly.
Should a venue install InkPlay on every PC on the first day?
The documented safer path is to begin with one or two test PCs, prove the complete session and recovery loop, then expand in controlled groups.
Does the owner website password also log branch staff into Controller?
No. Owner website access and local staff access are separate flows. Cashiers, supervisors, and admins should use individual staff accounts and role-appropriate permissions.
Is InkPlay onboarding fully automatic?
No. The current public path includes documented setup and direct contact, but branch identity, activation, device testing, staff permissions, and rollout approval still require operator decisions.
Need help with your venue?
Continue the conversation in the support center.
Choose the branch, describe what is affected, and keep every reply together until the issue is resolved.