KBYG, role-scoped: the Boarding Pass pattern, now native

When Black Coffee's team published their interactive KBYG for the 2025 North American tour, it did something every production team has tried and failed to do with a PDF: it gave each persona exactly the information they needed, scoped to their role, and let the production team update it the morning of the show.

We liked it enough to copy the pattern into the platform. Event guides are now a first-class module in ATLVS, rendered on both GVTEWAY (portal) and COMPVSS (mobile) from one source of truth, with zero duplication.

The problem with PDF KBYG

A PDF can't be scoped by role. A guest and a production carpenter see the same document. So you either write one bloated PDF that confuses the guest with SOPs and PPE they don't need, or you write three PDFs and try to keep them in sync.

A PDF also can't be updated at 9am on show day when the weather changes the load-in schedule. You can generate a new PDF, rename it, re-upload it to a link — and hope every stakeholder refreshes from the new one. They won't.

One source of truth, six persona renders

An event guide is a single row in event_guides per project × persona. The JSONB config column holds a typed list of sections: overview, schedule, set_times, timeline, credentials, contacts, faq, sops, ppe, radio, resources, evacuation, fire_safety, accessibility, sustainability, code_of_conduct, or custom.

In ATLVS CMS, you author one canonical guide. In the portal (GVTEWAY) and mobile (COMPVSS), a single <GuideView> component renders the sections that viewer's persona is entitled to see. A guest sees parking, schedule, FAQ. Crew sees radio channels, SOPs, PPE. Same data, filtered view.

Public guides readable by anon

Guests shouldn't need to sign up to read the KBYG. We added an RLS policy — event_guides_select_public — that lets anon read guides where status='published'. That's it. No link obfuscation, no anon token, no secret URL. The guide is public because it's supposed to be public, and the database enforces that cleanly.

What we kept from the Boarding Pass original

• Tier 1–5 classification banners for venue zones
• Role-based timeline views (artist vs. crew vs. security)
• Radio channel allocations surfaced per persona
• Offline-accessible on the crew phone via COMPVSS service worker

What we added

• CMS editor with draft → preview → publish flow
• Version history — roll back any publish from ATLVS
• Server-rendered PDF export for the handful of stakeholders who still print it
• Branded per project — logo, accent color, hero imagery overlay --p-accent

Start using it

Event guides are live on the Professional tier and above. Open any project in ATLVS, tap Guides, pick a persona, and you're in the editor. Read the full how-to at /guides/what-is-kbyg.