Go Portal and Cross-Service Linking Guide (connecting Booking, Membership, and Check-in)
This guide explains how the three services — Booking, Membership, and Check-in — relate to one another and how they are cross-linked, centered on the unified portal Go (go.unlockos.io/{slug}). Read it after you have configured the three services individually, when you want to sort out "which URL should I hand to guests?" and "where does each one connect?"
The concept: Booking, Membership, and Check-in each have their own app URL (
booking/member/checkin). Go is the "entrance (hub)" that bundles them into a single URL. Guests only need to remember one Go URL to reach booking, membership sign-up, or check-in, and after logging in they can manage all of their keys together in Key Hub. You can distribute the individual URLs, or bundle everything through Go.
The Big Picture (how the 3 services relate to Go)
┌─────────────────────────────────────┐
│ Go Portal / Key Hub │
│ go.unlockos.io/{slug} │
└───────────────┬─────────────────────┘
Logged out: service list / Logged in: Key Hub (unified key management)
│
┌───────────────────────────┼───────────────────────────┐
▼ ▼ ▼
┌───────────┐ ┌───────────────┐ ┌───────────────┐
│ Booking │ │ Membership │ │ Check-in │
│ booking │ │ member │ │ checkin │
│ .unlockos │ │ .unlockos │ │ .unlockos │
│ .io/{slug}│ │ .io/{slug} │ │ .io/{slug} │
└─────┬─────┘ └───────┬───────┘ └───────┬───────┘
│ Make a booking │ Become a member │ Enter on the day
│ │ │
└── Key Hub "Reservations" ─┴── Key Hub "Daily Keys" ───┴── Key Hub "Active"
(check in from your (one-tap unlock while (show QR / check out
upcoming reservations) subscribed) while checked in)
How Each Service Maps to Go
| Service | Individual app URL | Condition to appear on Go | How it looks in Key Hub |
|---|---|---|---|
| Booking | booking.unlockos.io/{slug} |
An active booking configuration exists | Reservations section (upcoming reservations; a "Check in" button appears from 24 hours before the reservation start) |
| Membership | member.unlockos.io/{slug} |
A membership plan exists | Daily Keys section (one-tap unlock while subscribed) |
| Check-in | checkin.unlockos.io/{slug} |
An active check-in configuration exists | Active section (show the QR code and check out while checked in) |
In addition, depending on the facility, Locker (
locker), Resident (resident), and Front Desk (frontdesk) may also appear in Go's service list.
Go's Two Faces: Logged Out (service list) and Logged In (Key Hub)
Logged out: the service list (portal landing)
When you visit go.unlockos.io/{slug} without logging in, you see a list of the services available at the facility.
| Icon | Service | Destination |
|---|---|---|
| Checkmark | Check-in | checkin.unlockos.io/{slug} |
| Calendar | Booking | booking.unlockos.io/{slug} |
| User | Member | member.unlockos.io/{slug} |
| Lock | Locker | locker.unlockos.io/{slug} |
| Home | Resident | resident.unlockos.io/{slug}/register |
| Monitor | Front Desk | frontdesk.unlockos.io/{slug} |
- If only one service is available, the portal screen is skipped and you are redirected directly to that service (no extra steps for the guest).
Logged in: Key Hub (unified key management)
Once you log in (via email OTP), all of your keys appear together in Key Hub in the bottom navigation. This is where the three services converge.
| Key Hub section | Corresponding service | Contents | Main action |
|---|---|---|---|
| Daily Keys | Membership | Keys you can use every day while subscribed | One-tap unlock |
| Reservations | Booking | Upcoming reservations | Check in (completed within Go) |
| Active | Check-in | Keys currently checked in | Show QR, check out |
| Past | Common to all services | History of completed check-ins | View only |
Sections with no keys are hidden. A member who uses all three services sees Daily Keys, Reservations, and Active all lined up in Key Hub.
URL Scheme (the foundation of cross-linking)
Every route is assembled around the Slug (the facility URL identifier). The Slug is set under "App URLs" in Basic Settings.
| Pattern | Behavior |
|---|---|
go.unlockos.io/{slug} |
Shows the service list (auto-redirects if there is only one) |
go.unlockos.io/{slug}/{app} |
Redirects directly to the specified service. {app} = checkin / booking / locker / resident / frontdesk |
booking.unlockos.io/{slug} |
Directly to Booking |
member.unlockos.io/{slug} |
Directly to Membership (the member app) |
checkin.unlockos.io/{slug} |
Directly to Check-in |
Example: go.unlockos.io/sakura-mansion/checkin redirects to the check-in app.
Old URLs (the format that includes
facilityId/configIdin the query) are automatically redirected to the Slug-based form. This keeps API keys and internal IDs out of public-facing URLs.
How to Set Up Cross-Linking (configuration steps)
The cross-links between Go and the three services are established automatically once you configure each service. There is no special "link settings" screen. The key points are these three:
1. Set the Slug (the foundation for everything)
Set the Slug under Basic Settings → App URLs. This aligns the URLs for go / booking / member / checkin under the same Slug.
2. "Enable" each service
- Booking: Create a booking configuration (plan config) → "Booking" appears on Go (Booking Setup Guide)
- Membership: Create a membership plan → "Member" appears on Go (Membership Setup Guide)
- Check-in: Create a check-in configuration → "Check-in" appears on Go (Check-in Setup Guide)
3. Distribute the Go URL / QR code
From the app URL list panel in Basic Settings, copy the go.unlockos.io/{slug} URL and QR code, and post them at your front desk, on your own website, and on printed materials.
Verify
- Opening
go.unlockos.io/{slug}shows all the services you enabled lined up in the list - Logging in shows the corresponding key sections lined up in Key Hub
Which URL Should You Distribute (guidelines for designing the flow)
| Who / when you want to distribute | Recommended URL | Reason |
|---|---|---|
| You want a single "entrance" for the facility | go.unlockos.io/{slug} |
Guides booking, membership, and check-in through one URL/QR. Members go straight to Key Hub on login |
| You want online bookings (OTA / your own website) | booking.unlockos.io/{slug}?config=<config-id> |
Goes straight to the booking form. You can attach a per-channel config ID |
| You want to recruit members | member.unlockos.io/{slug} |
Goes straight to the plan list (Landing) |
| You want to handle walk-ins at the front desk | checkin.unlockos.io/{slug} or a kiosk |
Goes straight to same-day check-in |
| You want a direct link to a specific service via Go | go.unlockos.io/{slug}/{app} |
Safely redirects directly, based on the Slug |
When in doubt, distribute Go (
go.unlockos.io/{slug}) — it is the most versatile. At facilities with only one service, guests are auto-redirected, so distributing Go doesn't add any extra screen.
Representative Flows Where the 3 Services Connect
Member → Booking → Check-in (full use)
- A member joins at
member.unlockos.io/{slug}(or "Member" on Go) - The member checks in daily from the SpaceCard in the member app, or does a one-tap unlock from Daily Keys on Go
- Reservations eligible for benefits are booked from the member app or from Booking (a free allowance may apply)
- Reservations are checked in from the Reservations section on Go (from 24 hours before start)
- While checked in, show the QR and check out from Active on Go
General guest → Booking → self check-in
- The guest books and pays at
booking.unlockos.io/{slug} - From 24 hours before the reservation start, a "Check in" button appears under Reservations on Go
- Check-in is completed within Go, and the access code (key) is displayed
Drop-in guest → walk-in
- Launch
checkin.unlockos.io/{slug}from the front desk QR / kiosk - Select a plan, pay, and get a key issued on the spot
- (The "Walk-in" tab on Go also redirects to the same check-in.)
Setup Completion Checklist
- The Slug is set, and the
go/booking/member/checkinURLs are aligned - Each service you enabled appears in the
go.unlockos.io/{slug}list - Logging in shows the corresponding key sections (Daily Keys / Reservations / Active) in Key Hub
- You have obtained the Go URL / QR code for distribution
- You have decided the flow (which URL to post where)
Frequently Asked Questions
Q: Can I skip Go and distribute only the individual URLs (booking / member / checkin)?
Yes. Each service's individual URL works independently. Go is a convenient hub when you want to combine multiple services into a single entrance.
Q: If I only have one service, won't distributing Go show an unnecessary screen?
No. When only one service is available, Go skips the portal screen and redirects directly to that service.
Q: No keys are showing in Key Hub
Check that the email address you are logged in with is correct, that your membership is active (Daily Keys), and that you have reservations registered (Reservations). Sections with no keys are hidden.
Q: I have a reservation but no "Check in" button appears
The check-in button appears from 24 hours before the reservation start.
Q: What happens if I change the Slug?
All of the old Slug's go / booking / member / checkin URLs stop working. Update any QR codes and links you have already distributed.
Q: Where are a membership subscriber's "Daily Keys" determined?
The foundation is the space where the member can check in (i.e., the check-in configuration). The check-in configuration tied to the member's plan appears as the SpaceCard in the member app / Daily Keys on Go. For details, see step 4 of the Membership Setup Guide.
Related Pages
- Go Portal / Key Hub Help — details on operating Go
- Basic Settings — check the Slug and all app URLs
- Booking Setup Guide
- Membership Setup Guide
- Check-in Setup Guide
- Member Home Screen / SpaceCard
- Guest Booking App / Guest Check-in