"Hi, I'm outside. How do I get in?"
I run Codeburg, an eight-desk coworking space in Burgas, Bulgaria. We don't have a smart lock yet, so when that message arrives, the person who answers is usually me.
I opened the space in 2025 because I needed somewhere near home to work. Two kids, a dog, and the usual round of autumn colds still make me glad I have it. I'm also a developer. When the coworking software I tried felt too heavy for eight desks, I built a simpler version, and it became OhMyDesk. Since then I've helped other small spaces connect their bookings to their door locks. This is what I learned from their doors, including what went wrong.
Dimitar Inchev from Coworkies told me about a community manager in London who looked after five or six locations. Nobody can stand at six doors. At a space like mine it is one door, on a Sunday morning, when I'm home with the kids.
Look at the door before you shop for a lock
Walk from the street to the desk the way a first-time visitor would. Can they get through the building entrance? Is there another door between the entrance and the room they booked? A code for the coworking door is no use if the street door is locked.
Take photos of the door, frame and existing hardware. Ask the landlord who can approve changes, and get a qualified installer to check compatibility and safe exit before you buy, especially for a shared entrance or a fire door. A retrofit that fits one door can be a poor choice for the next one.
For occasional guests, I'd start with a keypad. Nobody wants to download an app on the pavement. Check first that your lock can take one; some models can't. If you plan to send an unlock link instead, test it the way a guest will: outside, on mobile data, on a phone that has never had the lock app.
Then check how you'll manage the lock when you're not there. Depending on the model, that needs built-in Wi-Fi or a separate bridge. Ask the vendor to show a booking creating a code on your exact setup, and get the running costs in writing. Nuki's Smart Hosting, for example, is a subscription for each lock used with the service.
A small space we worked with in Germany used TTLock. When it linked its lock account, we could see a side entrance and a workshop door alongside the doors members needed. It was a good reminder to assign doors deliberately. A day pass shouldn't unlock the workshop just because the lock is on the same account.
Give the guest a code that fits the booking
Give each guest booking or member their own PIN. If somebody cancels, you can revoke that one code. A shared PIN tends to live on in old messages, and changing it means telling everyone who still needs it.
Set the hours before you automate anything. A day pass might follow your opening hours. A monthly membership might include weekends. If you allow an arrival buffer, keep it short. Set the expiry on the lock where the hardware supports it, and test early revocation as well. A code that expires on Friday is still a problem if the booking was cancelled on Tuesday.
We once tried to make the same PIN work across separate opening windows. The Nuki setup we tested rejected the duplicate PIN even though the windows didn't overlap. If your lock does that, decide how to handle split hours before you sell the pass. One long access window may also let someone in while the space is closed.
Send a code once the booking is paid or you've approved it, and once the system confirms it was created. Put the entrance, the access hours and a number someone will answer near the top of the message. If there are two doors that look plausible, a photo of the right one can save a phone call. If the code can't be created, someone on the team needs to hear about it before the guest turns up.
Rehearse a bad morning
One of the first spaces we connected stopped getting automatic codes about a week into testing. The lock was fine. The vendor's trial had ended, and nobody got a warning: not the owner, not us, not the guest waiting for a code. Two things would have caught it. A renewal date in the calendar catches the subscription. An alert on a failed code catches everything else.
Try the whole thing as a guest, from booking on your phone to typing the code outside. Then disconnect the bridge or internet connection in a quiet window and run three separate tests. Does a code you issued earlier still open the door? Can you issue a new one while the lock is offline? Can you revoke one? Reconnect it and check that your changes have reached the lock.
Arrange a backup that somebody nearby can actually use. If there's a mechanical override, test the key from outside and leave a spare with someone who can get there. Send battery alerts to a named person and keep the replacements somewhere they can reach. Put the support number on the door as well as in the email. Test that number too.
Give staff and installers their own accounts where possible. Decide who can see access logs, and tell members what you record and how long you keep it. If a code stops working, the person helping the guest should be able to see what happened without borrowing the owner's login.
Start with one door
I'd start with a single entrance and one type of pass. Make a booking, move it, cancel it, and try the old code. Ask somebody who's never been to the space to follow the arrival email while you wait inside. You'll learn more from where they stop than from another afternoon looking at lock specs. When Codeburg gets its lock, that is how I'll do it.
My favourite evenings at Codeburg usually involve beer, darts and a conversation that goes on long after I meant to leave. That's the part of running a coworking space I want to spend more time on. Opening the door is the bit I'm happy to hand over.
Alex Bodrov runs Codeburg, a small coworking space in Burgas, Bulgaria, and co-founded OhMyDesk.app, coworking software that connects bookings to smart locks.
