Access that follows payment
Someone buys a day pass at 08:15 and wants to get in at 08:20. That only works if access follows payment, with no step in between. In Doory, building access is set up automatically as soon as payment is received, and every step of that is logged.
Why this is the bottleneck in coworking
In office rental, access is an action at move-in, once per tenant. In coworking it is an action per sale, dozens of times a month, and usually at moments when nobody is at the front desk. If it becomes manual work, it doesn't happen on time, and someone ends up in front of a locked door with a valid pass on their phone.
What happens automatically
After a successful payment, Doory creates the person as a member with the right validity period, assigns the access groups that belong to the product purchased, and sets up those permissions with the building's lock supplier. When the day pass expires, access disappears at that moment.
The link to the product is the important part. A day pass gives access for one day to the spaces that belong to that product. A monthly membership gives access for longer, possibly to more spaces. You set this up once per product and per building.
Why everything is logged
Because a chain of automatic steps can only be trusted if you can see where it stops. For each sale you see: payment received, member created, access group assigned, permissions set up at the lock. If something goes wrong, for example a lock that is offline, you can see which step it is stuck on instead of having to guess.
That log is also your accountability. After an incident you can show who had permissions on which day and where they came from.
What it gives you
Coworking that simply keeps running early in the morning and at weekends, without anyone from your team having to be there. And no keys or codes left in circulation after a pass has expired.
Where the product stops
The hardware remains your lock supplier's. If the lock doesn't work, automatic provisioning won't fix that. But you will know within a few seconds that the problem lies with the lock and not with the permissions.