Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.1club.ai/llms.txt

Use this file to discover all available pages before exploring further.

The WebLock integration ties 1Club to the Valnes WebLock physical access control system. Members and bookings in 1Club become access grants in WebLock - the right doors open at the right times without staff handing out PINs or fobs by hand. Area-to-device mappings also let you drive WebLock light rules from the booking schedule.

​
Before you start

  • A WebLock (Valnes) account with a Business ID and groups and readers already configured in the WebLock console.
  • The list of groups and readers you intend to map - 1Club fetches them after you connect, but knowing what each one represents on the physical side makes mapping faster.

​
Connect WebLock

  1. Go to Settings → Integrations and click Activate on the WebLock card.
  2. Enter your Business ID.
  3. Adjust the two buffer values if you want (defaults are sensible):
    • Grant Buffer Minutes (0-120, default 15) - how long before a booking starts that access becomes valid, and how long after it ends that it remains valid.
    • Rules Buffer Minutes (0-120, default 5) - how long before/after a booking the area’s light or device rules apply.
  4. Click Test connection to verify the Business ID and confirm 1Club can reach WebLock.
  5. Save.
Once the connection tests successfully, the Group mapping and Device mapping sections become editable.

​
Group mapping

Group mapping decides which WebLock access group is granted for each entitlement in 1Club. Every mapping is optional - leave a row as — to skip it.
  • Plans → group - which group active members on each plan belong to. Most operators map “Standard” plan to “Members” and so on.
  • Area type → group, Class type → group, Instructor type → group - which group a one-off booking grants. Pick whichever axis matches how you organize doors.
  • Default group - fallback group used for any booking that does not match a mapping above.

​
Device mapping

Device mapping is independent from group mapping and drives WebLock light rules.
  • Area → reader/device - assigns one WebLock reader to each 1Club area. When a booking starts in that area, the reader’s lighting rule applies (e.g. turn on lights, indicate occupied).
Leave — to opt an area out of light rules.

​
What syncs

  • New memberships and bookings create access grants in WebLock, with a PIN generated per grant.
  • Cancelling a booking or expiring a membership revokes the corresponding access grant.
  • Light/device rules apply on the buffer schedule you configured.
  • Access grants and the events from readers (door opened, denied) are visible under Settings → Access Control in 1Club.

​
Disconnect

Click Deactivate on the integrations list. This stops 1Club from creating new grants in WebLock. Existing grants in WebLock are not retroactively removed - delete or expire them in the WebLock console if needed.

​
Troubleshooting

  • Test connection fails - the Business ID is wrong, or your WebLock account has no API access. Confirm with your WebLock administrator.
  • Group dropdowns are empty - “No WebLock groups available. Verify the Business ID and test the connection.” Re-run Test connection after fixing the Business ID.
  • Member can’t open the door - check Settings → Access Control for the access grant. If it’s missing, the plan or booking may not be mapped. If it’s there but validFrom is in the future, lower the Grant Buffer Minutes.
  • Lights don’t come on for a booking - the area is not mapped to a reader in Device mapping, or the Rules Buffer Minutes is larger than the time until the booking starts.