Multi Counter on Pro: Pinning Cloud Counters, Sharing the Grid, and Controlling Which Ones Are Public

Multi Counter is a single page that shows several of your cloud counters at once. You add and subtract on each one in place, the values sync to the cloud the same way they do on the individual counter pages, and one shared link can broadcast the whole grid to spectators in real time.

It is genuinely just a view. There is no "new counter type" to learn — every card on the Multi Counter page is the same Standard or People counter you already use on its own page, rendered side by side. If you change a value on Multi Counter, the dashboard row updates. If you change it on the dashboard, the Multi Counter card updates. They are the same record.

The reason the page exists is the same reason a tally sheet has more than one column. Three gates at the same event, two scoreboards at the same tournament, a few separate counts that belong together — Multi Counter is for situations where you would rather glance at one screen than switch tabs.

The thing that surprises new Pro users most often is that you do not create counters on the Multi Counter page. The grid is a curated subset of counters you already have. You build it by pinning existing cloud counters from your dashboard.

Think of it as the home screen of a phone. You have a hundred apps installed; you put a handful on the home screen because those are the ones you want at a glance. The other apps still exist — they're in the app drawer. Same idea: every counter you create lives on the dashboard, and pinning one makes it appear on the Multi Counter grid as well.

Unpinning is just as cheap. It removes the counter from the grid; the counter itself stays on the dashboard with all its history intact. You can pin and unpin whenever you want — there's no penalty for changing your mind.

From your dashboard:

1. Find the counter you want to pin in one of the per-type tables (Standard Counters, People Counters, etc.). Each row has a small thumbtack icon on the right side, alongside the Open / Settings / Delete buttons.

2. Click the thumbtack. It fills in to indicate the counter is now pinned. The Multi Counter row at the top of the dashboard updates immediately to include the new card.

3. Open /counters/multi-counter (or click the Multi Counter row's "Open grid" button) to see the pinned counters laid out in a grid.

Unpinning is the same click — the filled thumbtack toggles back to outline, and the counter drops out of the grid. The dashboard row stays put.

The order of pins is the order you pinned them. There is no drag-to-reorder yet. If the order matters to you, unpin and re-pin in the order you want.

The header on the Multi Counter page reads "Multi Counter" by default. Click on it (or click the small pencil icon next to it) and you can type a custom title — the name of your event, the venue, the campaign, whatever makes the page recognizable to you.

This title is not just for you. When you mint a public share link for the grid, the title travels with it: spectators see the same name at the top of their view. "Multi Counter" reads as generic; "Spring Festival 2026 — Front Gate" tells your client what they're looking at.

You can edit the title from two places — the Multi Counter page header itself, and the input at the top of the share modal. Both write to the same field. Hit Enter or click out of the box to save; a green check confirms.

If you change the title after a share link is already live, the spectator's view picks up the new name within a few seconds — no need to re-mint or rotate the link.

On the Multi Counter page there is a "Share Grid" button next to the page title. Click it, and a modal opens with a single public URL — that URL is read-only, anyone can open it, no login required. They will see the same counters you do, with the values updating live.

A few rules to keep in mind:

One active link per user. You don't accumulate a list of grid share links the way you might per-counter. Generating a new one rotates the old one — the old URL stops working, and anyone holding it gets a 404. This is intentional: it makes "reset access for the whole event" a single click rather than a list-management chore.

Revoke kills it instantly. The modal has a Revoke button that takes the link offline immediately. Use it at the end of a shift or an event if you don't want the URL working any more.

Spectators only get a viewing experience. They cannot increment, decrement, settings-edit, or change anything. If you want someone to be able to write to a specific counter, generate an edit-link on that individual counter — the per-counter share modal handles that and is described in the cross-device guide.

Here is the part that catches people. The grid spectator does not show every counter you've pinned. It shows the counters you have pinned AND marked as public.

Each Standard cloud counter has its own Public / Private visibility setting, set from the share modal on the counter (covered in detail in the per-counter sharing section of the cross-device guide). When you mint or load a grid share link, the spectator sees:

• Every Public counter you have pinned to your grid.
• No Private counters, even if they are pinned.
• People counters always pass through (their share-link system is per-link rather than a single Public flag — again, see the cross-device guide).

Pinning and visibility are separate switches. Pinning controls what shows up on your Multi Counter page; visibility controls what shows up in the public spectator view of your grid. If you want the grid share to show fewer counters than your full pinned set, set the ones you want to hide to Private. Toggle the flag back to Public and the counter rejoins the spectator's view on the next poll — no need to revoke or re-mint the grid link.

A practical example: at a concert with three gates and a VIP entrance, you might pin all four counters so you can see them at a glance — but only mark the three main gates as Public. The VIP count goes into the same overall total but does not appear on the screen your client is watching from front-of-house.

Counter names are editable inline. On a Multi Counter card, click directly on the name in the card header and type a new one. A small status badge confirms the save with a green check (or shows a red icon if something went wrong, with a hover-tooltip describing the failure).

The new name reaches every surface the counter appears on: the dashboard row, any other open tabs of the Multi Counter page, the dedicated counter page, and within a few seconds, the public spectator view if the counter is shared. You do not have to rename the counter in multiple places.

"My pinned counter is not showing in the share." Check the counter's visibility — if it is Private, the spectator does not see it. Open the counter's share modal, switch to Public, save. The grid share picks it up on its next poll without you having to revoke or re-mint.

"I revoked a share link by accident." Mint a new one. Spectators on the old URL will get a 404 and you will need to redistribute the new URL to anyone who needs access. There is no undo.

"The grid title I set on the share modal isn't appearing on the Multi Counter page." Refresh the Multi Counter page. The two inputs are tied to the same database field, but the page header doesn't poll for it — a hard refresh syncs them up. Going forward (after editing once), both views stay current.

"My volunteer can see the count but can't change it." Correct — grid share links are view-only by design. If you want them to be able to add to the count, send them a per-counter edit link instead, generated from the individual counter's share modal. The cross-device guide walks through that flow.

"I unpinned a counter and now the share spectator shows fewer counters." Yes — the grid spectator reads the live pin set every poll, so unpinning here removes the counter from there too. No need to revoke or re-mint.

A first-event-on-the-grid configuration:

Create the cloud counters you need on the dashboard — one per gate, one per zone, one for the running total if you want a roll-up.

Pin each counter to your Multi Counter grid by clicking the thumbtack on its dashboard row. The Multi Counter row at the top of the dashboard updates as you go.

Name your grid by clicking the title at the top of the Multi Counter page — something that identifies this event so the spectator URL doesn't read as generic.

Decide which counters need to be visible on the public broadcast. For each one you want public, switch its visibility toggle to Public.

Click "Share Grid," copy the URL, and load it on whatever screen the client or the production team will watch — TV in the trailer, tab on the venue manager's laptop, an OBS browser source for streaming.

For anyone who actually needs to add to the count from their own device, generate per-counter edit links from each individual counter's share modal — that mechanic, including how to name the links and revoke them at end-of-shift, is covered in the cross-device guide on per-counter share links. Grid share links are view-only by design and won't give a volunteer write access; that's what the per-counter edit links are for.

At the end of the event, two clicks of cleanup: revoke the grid share link from the Share Grid modal, and revoke any per-counter edit links from their respective modals.

The whole sequence takes longer to write down than to do. Once you've run it once, the second event is a few minutes of setup.

The two ideas to keep separate in your head are pinning and visibility. Pinning is for you — what shows up on your Multi Counter page. Visibility is for them — what shows up on the public spectator view of your grid. Anything you've pinned that is also marked Public is visible to spectators. Everything else stays between you and your dashboard.

If you have already created your cloud counters but haven't pinned anything yet, the dashboard is where to start. If you haven't yet upgraded, the pricing page explains what is included. If you want to read the companion piece on multi-device sync and per-counter share links, the cross-device guide covers the parts of the system this article assumes.