InkPlayWiki

Bring your first branch online

Published: 2026-07-12 - Updated: 2026-07-13 - 12 min read - InkPlay Team

A practical launch path for opening the first InkPlay branch with owner access, Controller, Agent PCs, staff roles, setup, and a test session.

What should I set up before staff use InkPlay with real players?

Your branch has a clean first-day path: owner account, branch profile, Controller, Agent PCs, staff access, and a verified session loop.

Before you start

  • Create the owner account and branch.
  • Install and activate the Controller.
  • Choose one or two test PCs before rolling out every station.

Prepare the branch profile

Start with the branch identity and the business rules staff will use every day. This keeps setup tied to the real venue floor instead of a demo-only configuration.

  • Confirm branch name, contact details, city, country, and owner access.
  • Decide first PC groups, station names, opening hours, and cashier expectations.
  • List the first staff roles before inviting staff users.

Configure the first operating basics

Before real customers arrive, configure the minimum data staff need to run sessions consistently.

  • Set store profile and visible branch identity.
  • Create PC types and time types that match the first pricing model.
  • Create or confirm staff accounts and permissions.

Install Controller and Agent

The Controller is the staff workspace. Agent is the player-facing PC shell. Install both early so setup decisions are tested through the real branch loop.

  • Install Controller on the counter machine or staff workstation.
  • Install Agent on a small group of test PCs before rolling out every station.
  • Confirm each Agent appears online and belongs to the right branch context.

Run the first test session

Test the full session path from staff action to player screen and reporting history before using InkPlay with real customers.

  • Start a guest session from the Controller and confirm the Agent screen updates.
  • Extend, transfer, and stop the session to prove staff actions are clear.
  • Review the session history and cashier visibility after the test is closed.

Verify it worked

  • At least one Agent PC appears online and approved.
  • A test session can be started, extended, stopped, and found in history.
  • Staff can sign in with the right permissions and see the pages they need.

Troubleshooting

The test PC does not appear in the Controller.

Confirm Agent is installed, the PC is on the same branch network, and the device setup page shows pending or approved devices.

Staff can sign in but cannot find the right pages.

Review permissions and Controller menu management before training staff on daily workflows.

See also