InkPlay Wiki: Sections and Overviews
About InkPlay
This wiki collects operator manuals for the InkPlay platform. Start here when you want a clean explanation of what each module does, how a venue gets online, and which guide matches the job your staff need to finish.
Sections
| Section | What it covers |
|---|---|
| What is InkPlay?About InkPlay | A plain explanation of InkPlay as a local-first operating platform for gaming venues, staff, player PCs, mobile identity, and displays. |
| InkPlay system overviewAbout InkPlay | Understand how the cloud platform, Controller, Local Node, Agent PCs, mobile app, and displays fit together without exposing internal engineering details. |
| Understand local-first branch operationsAbout InkPlay | Understand why InkPlay keeps branch-critical work local first while cloud services support subscriptions, releases, reporting, backups, and owner visibility. |
| InkPlay roles and permissionsAbout InkPlay | Understand owner, admin, staff, and player responsibilities before granting access to branch controls, reports, setup, and sensitive pages. |
| InkPlay glossaryAbout InkPlay | A simple glossary for common InkPlay terms such as branch, Controller, Local Node, Agent, session, package, display, and player account. |
| Create the owner accountGetting Started | Create the first InkPlay owner account and use it as the trusted starting point for branches, billing, downloads, and admin access. |
| Create the first branchGetting Started | Create the first venue branch so Controller, Agent PCs, staff, billing, and reports have the correct operating context. |
| Install the ControllerGetting Started | Install the InkPlay Controller on the branch staff machine so the venue can run setup, sessions, staff work, devices, reports, and Agent tools. |
| Activate the branch ControllerGetting Started | Connect the local Controller installation to the correct InkPlay branch before staff start live setup or sessions. |
| Bring your first branch onlineGetting Started | A practical launch path for opening the first InkPlay branch with owner access, Controller, Agent PCs, staff roles, setup, and a test session. |
| Invite staff and assign rolesGetting Started | Create staff access for cashiers, supervisors, and admins without exposing owner-only or sensitive branch controls. |
| Manage the Controller menuGetting Started | Shape the Controller sidebar so staff can find daily pages quickly while permissions still protect sensitive actions. |
| Set Controller languageGetting Started | Choose the Controller language and keep staff labels understandable across English and Arabic branch workflows. |
| Set up the store profileBranch Setup | Configure the branch identity staff and players will see across Controller, receipts, displays, and customer-facing surfaces. |
| Set up PC typesBranch Setup | Create PC types that match the branch floor, hardware tiers, pricing expectations, and staff language. |
| Set up time typesBranch Setup | Create the time and pricing labels staff use when selling playtime, packages, extensions, and session durations. |
| Set up devicesBranch Setup | Approve and organize branch PCs so the Controller can show the right station names, states, types, and Agent connectivity. |
| Set up Agent PCsBranch Setup | Prepare player PCs with the InkPlay Agent shell, game library, session status, wallet visibility, support actions, and venue-safe promotions. |
| Set up console stationsBranch Setup | Prepare console areas, station names, pricing expectations, and customer-facing display behavior for non-PC gaming zones. |
| Configure console pricingBranch Setup | Set console pricing defaults so staff can sell console sessions without mixing them with PC time or custom counter work. |
| Configure permissions and page accessBranch Setup | Control which staff can use sensitive pages such as setup, pricing, reports, audit, staff, security, and menu management. |
| Configure security policiesBranch Setup | Review branch security settings that protect player PCs, staff access, browser behavior, downloads, tools, and session end behavior. |
| Use backupsBranch Setup | Use branch backups as an operator safety habit for setup recovery, support handoff, and safer changes. |
| Use the branch dashboardDaily Operations | Use the Controller dashboard as the daily starting point for PC state, branch readiness, active sessions, warnings, and staff handoff. |
| Run paid sessions and time packagesDaily Operations | Use InkPlay to start paid playtime, sell packages, extend sessions, transfer players, and keep cashier history connected. |
| Run cashier shiftsDaily Operations | Use shifts to make cashier responsibility, opening balance, closing review, and handoff clearer. |
| Handle counter sales and store requestsDaily Operations | Use the counter and store menu flow for snacks, products, requests, and branch sales that happen beside playtime. |
| Manage inventory and store menuDaily Operations | Keep branch products, store menu labels, availability, and sales readiness clear for staff and player-facing requests. |
| Manage player accountsDaily Operations | Use player accounts for returning customers, balances, activity, branch history, QR login, debts, and support context. |
| Handle recharges and balancesDaily Operations | Apply player recharges, balances, and wallet-related actions without losing cashier context or account history. |
| Track player debtsDaily Operations | Use debt tracking carefully for trusted customers, partial payments, and owner-visible cashier history. |
| Use prizes and pointsDaily Operations | Use points or prize-related records to support loyalty, rewards, and player history without confusing them with cash balance. |
| Handle player PC requestsDaily Operations | Review and respond to player requests for PCs so staff stay in control while customers get a smoother flow. |
| Review reports and performanceDaily Operations | Use reports to understand sessions, sales, customers, performance, and branch trends without interrupting live floor operation. |
| Review audit logsDaily Operations | Use audit logs to understand important changes, staff actions, and branch events when owners need accountability. |
| Use Agent file managementAgent Tools | Use Agent file tools for support and operational inspection without treating player PCs like unmanaged personal machines. |
| Monitor Agent PCsAgent Tools | Use Agent monitoring to understand screen state, PC readiness, support needs, and player-facing issues from the Controller. |
| Use Agent process controlAgent Tools | Review and manage running processes on Agent PCs when games, launchers, or stuck apps need staff support. |
| Manage Agent gamesAgent Tools | Create and maintain the game cards, launchers, categories, artwork, and visibility that players see on Agent PCs. |
| Use the shared game libraryAgent Tools | Use a branch-shared game library path when the venue wants Agent PCs to launch games from a controlled shared location. |
| Manage game updatesAgent Tools | Use game update tools to plan, stage, and monitor game update work without interrupting live customer sessions. |
| Configure the Agent shortcut menuAgent Tools | Configure player-facing shortcuts so customers can access approved actions, apps, support, and store surfaces from the Agent shell. |
| Moderate Agent streamsAgent Tools | Review streamer and live content placement so Agent stream surfaces stay venue-safe and aligned with the branch audience. |
| Check PC health and device readinessAgent Tools | Use PC health signals to decide which stations are ready, offline, unhealthy, under maintenance, or unsafe to sell. |
| Use mobile QR login and player accountsPlayer And Mobile | Help players use the mobile app, scan PC QR codes, link branch accounts, and keep sessions tied to the correct player identity. |
| Link player branch accountsPlayer And Mobile | Connect a mobile player identity to the right branch customer record so balances, activity, rewards, and session history stay useful. |
| Handle mobile PC requestsPlayer And Mobile | Use mobile PC requests as a staff-controlled queue for players who want a station, package, or branch response. |
| Review player activityPlayer And Mobile | Use player activity to answer account questions, understand return visits, and support mobile-facing branch history. |
| Use support reports and notificationsPlayer And Mobile | Handle player support reports, branch notices, and mobile notifications in a controlled, operator-safe way. |
| Pair TV displaysDisplays And Promotions | Pair venue TVs or console screens with InkPlay so staff can show station status, timing, queue context, and approved promotion surfaces. |
| Use display mode and customer screensDisplays And Promotions | Choose what customer-facing screens show for console stations, venue status, brand visuals, queues, and promotion content. |
| Understand promotionsDisplays And Promotions | Use InkPlay promotion surfaces for branch offers, venue displays, mobile messages, events, and player-facing campaign visibility. |
| Use branch offers and mobile pushDisplays And Promotions | Publish branch offers and mobile push messages with clear targeting, timing, and staff awareness. |
| Understand offline and reconnect behaviorMaintenance | Know what staff should check when branch services, Agent PCs, or customer-facing screens lose connection and later reconnect. |
| Handle Controller service unavailableMaintenance | Use a calm staff checklist when the Controller cannot reach local branch services or live operational data. |
| Manage releases, updates, and installersMaintenance | Plan InkPlay updates and installer work around venue hours so branch operation stays predictable. |
| Use backup and restore recoveryMaintenance | Prepare branch backup and restore routines so owners can recover from device failure, wrong changes, or service disruption. |
Quick paths
Owner setup
Create the owner account, prepare the branch, install Controller, activate it, and bring the first branch online.
Cashier daily work
Follow the normal front-desk flow for dashboard checks, paid sessions, shifts, counter sales, and player balances.
Agent technician flow
Prepare PCs, manage games, keep the shared library current, run updates, and confirm each PC is healthy.
Displays and promotions
Pair TV displays, choose display mode, understand promotion surfaces, and publish branch offers.
Maintenance
Handle offline recovery, service availability, releases, setup backups, and restore checks.