Manager Mobile Organizer · Table official 4 min
Pair an iPad in Manager Table mode Mint a table-device code, enter Table mode on iPad, verify the locked queue, and call the operator when the table needs help.
Feature-gated Beginner 6 steps en-CA Captions + transcript
Learning path Organizer launch path View path progress → ▶ Watch≡ ReadBoth formats use the same source-verified steps.
iM Feature-gated operator surface
Feature-gated operator surface
Live · Table devices LIVE DATA Table 3 No device paired READY
! Do not promise this workflow unless the deployment enables IMATCH_MANAGER_V2_SHELL.
Pair device
Source-verified interface illustration · labels reflect the current implementation CC Before event day, confirm that the Manager release has its V2 operator shell enabled. The Table devices pairing sheet is feature-gated today.
01 Verify release availability Enable the operator-side Table devices surface The pairing sheet is currently in the feature-gated V2 Manager shell. Confirm that this release has the V2 shell enabled before venue setup.
01 Enable the operator-side Table devices surface 0:00 02 Mint the one-time QR or pairing code 0:38 03 Choose Table mode on the iPad 1:12 04 Scan the QR or type the code 1:44 05 Verify Locked to and connection status 2:26 06 Call the operator—do not use Table mode for scoring yet 3:10 ← Previous Play guide Next →
← → navigate Space play/pause M narration F fullscreen
Step-by-step tutorial 1 Verify release availability Enable the operator-side Table devices surface The pairing sheet is currently in the feature-gated V2 Manager shell. Confirm that this release has the V2 shell enabled before venue setup.
iM Feature-gated operator surface
Feature-gated operator surface
Live · Table devices LIVE DATA Table 3 No device paired READY
! Do not promise this workflow unless the deployment enables IMATCH_MANAGER_V2_SHELL.
Pair device
Source-verified interface illustration · labels reflect the current implementation 2 Keep the table identity visible Mint the one-time QR or pairing code Choose Pair device for the correct table. The desktop displays a QR and one-time code that can be cancelled or replaced.
One-time enrollment
Pair Table 3 LIVE DATA Pairing QR Expires shortly READY
Cancel pairing Show code
Source-verified interface illustration · labels reflect the current implementation 3 Enter the table-device role Choose Table mode on the iPad The iOS login surface has a dedicated Table mode entry. It bypasses the Firebase operator workspace for this device role.
iPad login
iMatch Manager TABLE Sign in as operator Table mode
Source-verified interface illustration · labels reflect the current implementation 4 Pair this iPad to the table Scan the QR or type the code Use Scan pairing QR on iPad or type the code. After pairing, the app recommends that the operator manually enable Guided Access.
iM Pair this iPad to a table
Pair this iPad to a table
Table mode TABLE ! Guided Access is operator-controlled; the app cannot enable it automatically.
Pair Scan pairing QR
Source-verified interface illustration · labels reflect the current implementation 5 Confirm the table and queue Verify Locked to and connection status A paired device shows only its assigned table queue. Connected is healthy; Reconnecting means the heartbeat is stale or resuming.
Umpire pad · Connected
Locked to TABLE 3 TABLE WS Open · R1 Now NOW
MS Open · R2 Up next 05:30
Call operator
Source-verified interface illustration · labels reflect the current implementation 6 Respect the current boundary Call the operator—do not use Table mode for scoring yet Call operator flags the Manager live console. Start match is disabled and the current UI says scoring lands in the next update.
Read the Table mode boundary → Umpire pad · Connected
Locked to TABLE 3 TABLE WS Open · R1 Players are ready NOW
! Scoring lands in the next update.
Start match · Disabled Call operator
Source-verified interface illustration · labels reflect the current implementation Use it anywhere Share, embed, or export Deep links preserve the current step. Embedded tutorials follow this site's access policy.
Share / copy link Copy embed Print / PDF Download Markdown Download captions
Transcript and step index 6 chapters · searchable on this page 0:00 Enable the operator-side Table devices surface Before event day, confirm that the Manager release has its V2 operator shell enabled. The Table devices pairing sheet is feature-gated today. 0:38 Mint the one-time QR or pairing code Choose Pair device for the correct table. Manager displays a one-time QR and code for that table assignment. 1:12 Choose Table mode on the iPad On the venue iPad, choose Table mode from the Manager login screen. This enters the focused table-device workflow. 1:44 Scan the QR or type the code Scan the pairing QR or type the code, then tap Pair. If the iPad is used as a kiosk, manually enable Guided Access after pairing. 2:26 Verify Locked to and connection status Confirm the large Locked to Table 3 label and the assigned queue. Treat Reconnecting as a prompt to check the venue network. 3:10 Call the operator—do not use Table mode for scoring yet Use Call operator when the table needs help. Stop the workflow here: Table mode scoring is not implemented in the current release. Knowledge check
What should a table official do when the current Table mode needs intervention? A Enter a scoreB Use Call operatorC Unpair the deviceD Create a tournament
Documentation feedback Was this tutorial helpful? You can submit feedback anonymously without names, contact details, IP addresses, or device identifiers.
Yes, it helped Not yet
Product evidence Verified 6 steps against source Verified against repository commit d95a40d1. Interface illustrations use current product labels; screenshot frames use synthetic XCUITest fixture data.
apps/manager-mac/Sources/iMatchManager/Auth/LoginView.swiftapps/manager-mac/Sources/iMatchManager/Pad/PadPairingView.swiftapps/manager-mac/Sources/iMatchManager/Pad/PadQueueView.swiftapps/manager-mac/Sources/iMatchManager/ShellV2/Live/TableDevicesSheetV2.swiftapps/manager-mac/Sources/iMatchManager/ShellV2/FeatureFlags.swiftReview feature status and boundaries →