Setting up a Codelocks smart lock with Pitchbooking

Edited

Connect a Codelocks smart lock to Pitchbooking to give bookers timed access to the appropriate facility. This guide is for facility managers setting up a compatible lock.

Before you begin

  1. Contact your Pitchbooking Account Manager to discuss the facilities or amenities that need access and confirm a suitable lock and installation arrangements.

  2. Arrange installation with Codelocks or a suitable installer. Your Account Manager must enable Locks for your account before setup in the dashboard.

  3. Arrange to be on site with each installed lock. Have its model, master code and the name of the relevant facility ready.

Add and connect the lock

  1. In the Manager Dashboard, open Company Settings → Lock Control and select Add Device.

  2. Enter the lock model, master code and a name that identifies the lock, such as the site or facility name. Select Create Device.

  3. Enter the sequence shown in the dashboard on the physical lock keypad. Hyphens in the displayed sequence represent lights and are not entered.

  4. Select Generate Keycode, enter the generated code on the lock and check that it opens.

  5. Select Edit Device, attach the lock to the relevant facility and set any access offsets required. Select Save Changes.

  6. Repeat for each lock. Test the connection and facility association before relying on it for customer access.

How access works

Pitchbooking generates a keycode for access associated with a booking. Codes can be sent on the day of the booking or included in the confirmation email, and bookers can also find them in My Bookings. Offsets control the access window around the booking; agree suitable timings with your Account Manager.

Need help?

If Lock Control is unavailable, a code does not work, or you need help selecting or installing a lock, contact your Pitchbooking Account Manager. Keep master codes secure and do not share them with bookers.

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.