Reading paths by role

Not everyone needs every guide. Use the paths below to read in a sensible order for your job—then open other articles when a task needs them.

Across the library, Member Access OS follows Join, Pay (or proof of payment), and Visit, with support for recurring, credit-based, and hybrid billing shapes—the same backbone, bent to fit each brand.

Paths link to the same library as the main docs index: start with what shapes your decisions, then add deployment material only when you own hardware or go-live cutover.

Shared first steps (any role)

Org decisions — Skim the table of contents; read the rows that match how you pay, approve members, and handle entry. Note how long rollouts often take so calendar expectations line up with leadership.
Optional professional services — If you are buying help beyond software setup, use this to compare offers and ask clear questions.
Go-live handover — Before you run day-to-day operations alone, confirm you have what this checklist describes (even if your title is not “owner”).

You care about: scope, timing, budget for services, who signs off when the system goes live.

Step	Guide	Why
1	Org decisions (full pass)	Aligns sponsor expectations with what the product actually configures.
2	Implementation timeline	Sets calendar expectations for leadership and facilities.
3	Professional services	Frames pass design, training, venue work, and integrations you might fund.
4	Go-live handover	Defines what “done” looks like before your team operates without the implementation partner.

Operations lead, GM, or front-desk manager

You care about: approvals, member trouble, packages, and how day-to-day policy matches the software.

Step	Guide	Why
1	Org decisions — sections on payments, approvals, membership products, email	Connects how you run the desk to how the system behaves.
2	Go-live handover	Confirms you know where settings live and who to call after launch.
3	First client preflight (role-based) — skim only sections tied to flows you operate (payments, approvals, staff gate logs)	Spots mismatches between policy and configuration before opening the floodgates. Ignore hardware rows if you run staff-assisted entry only.

Facilities, IT, or door-entry partner

You care about: readers, cabling, labeling, commissioning, safe cutover—not member marketing copy.

Step	Guide	Why
1	Fleet and device naming	Keeps Asset labels aligned with Admin so support incidents are decipherable.
2	Preflight checklist (role-based) — §0 (facility) · §7 (unattended entry)	Confirms cabling, power, and gate behavior line up without naming a single vendor SKU.
3	On-site install runbook	Clarifies what a short install visit assumes was done before arriving on site (bench staging, configs).

If someone on the project prefers named hardware examples, optionally cross-check the detailed preflight checklist.

Marketing or member communications

You care about: what you can promise publicly (wallet, tap-to-enter), consistent language from ad → signup → confirmation email.

Step	Guide	Why
1	Org decisions — digital wallet and physical access sections	Matches claims to deployed capabilities.
2	Professional services — passes, site journeys	Clarifies optional help for creatives and UX so campaigns do not outrun deployment.
3	Headless landing API	When marketing or an agency builds a site on your domain using the public branding/content API.

Finance or billing administrator

You care about: how payment lines up before and after activation, exports, downstream systems.

Step	Guide	Why
1	Org decisions — payments, plans, membership products	Ties treasury reality to dashboard behavior.
2	Professional services — rollout planning, integrations	Surfaces data handoffs and reporting help you may contract.

Implementation or technical lead (short path)

You care about: verification, repeatability, and traceable device identity.

Step	Guide	Why
1	First client preflight checklist	Full profile-dependent verification list.
2	Role-based preflight	Vendor-neutral parallel when you document generically.
3	Fleet registry + on-site install runbook	Naming plus field timing when hardware ships.

Documentation home — all articles grouped by category (business first, then rollout, then technical).