What you will learn
- Doors, zones, and access levels in a coworking building
- Keyless methods: cards, phones, codes, and biometrics
- Member, team, guest, and staff permissions
- Time rules: 24-hour access, night rules, and holidays
- Visitor and delivery access handling
- Logs, incidents, and access reviews
What access control actually governs
A coworking building has many doors with different rules. The front door may welcome members around the clock. Meeting rooms may open only to the member who booked them, plus their guests, for the booked hour. Private offices open only to their tenants. Server and store rooms open only to staff. Access control turns those rules into permissions per person, per door, per time, and records every entry. A single shared code on the front door is not access control; it is a secret that every former member still knows.
Time rules add a second dimension. A member on a business-hours plan should not enter at midnight; a 24-hour member should. Holiday closures, event nights, and maintenance windows all change who may enter when. The system must apply those rules automatically, because front-desk staff cannot watch every door, and a rule enforced only when someone remembers is not a rule.
- Per-person, per-door, per-time permissions, not shared codes
- Zones: public, member, booked-room, private-office, staff-only
- Time rules for plan types, nights, holidays, and events
- Entry logs recording who opened which door, when
Core features members, staff, and operators need
For members, access must be frictionless: a phone or card that opens their doors without a second thought, and a clear route when it fails — a desk contact, a fallback code, or an intercom — rather than being locked out at midnight. Temporary access for guests should be grantable by the host member or by staff, time-limited, and revocable. Members should be able to see their own access rights, so a missing permission is spotted before it matters.
For staff, the essentials are permission management tied to membership, door status views, and log review. When a member joins, pauses, or leaves, permissions should change with the membership, not through a separate manual step that gets forgotten. Incident review — who entered a room at a given time — needs searchable logs. Door fault alerts should reach staff before members report being locked out.
- Phone or card access that works without a second thought
- Guest access grantable by hosts, time-limited, revocable
- Permissions changing automatically with membership status
- Door status views, searchable logs, and fault alerts
How the build runs, phase by phase
The build starts with a door survey: every door, its current lock, its wiring, and its required rule, agreed with the operator and building management. Hardware selection follows the survey, since doors vary — a glass front door, a fire door, and a meeting room door need different hardware. Permission rules are mapped per plan and per zone before any software configuration, because hardware installed on unagreed rules gets reconfigured later at cost.
Development and installation then proceed door by door or zone by zone, with member credentials issued and tested during a pilot period where old and new access run together. Staff training covers permission changes, guest grants, log review, and fault handling. Cutover should avoid a busy Monday morning; a quiet period lets faults surface without locking out a full building.
- Survey every door: lock, wiring, and required rule
- Map permissions per plan and per zone before configuration
- Pilot with old and new access running together
- Cut over in a quiet period, not on a busy Monday
Tech considerations that shape the result
Offline operation is the key technical requirement. Door controllers should keep working from cached permissions during a network outage, so a failed internet connection does not lock out a building. Credential security matters: phone credentials should be revocable remotely, lost cards deactivatable instantly, and codes rotated when staff change. Hardware choice should favour standard, replaceable parts over proprietary locks that tie the building to one vendor.
Integration with member management is what makes permissions reliable. Join, pause, cancel, and plan change should all flow into access without manual steps. Logs need retention rules and access controls of their own, since entry logs are personal data. If the building has existing security systems — alarms, cameras — access events should align with them rather than contradict them.
- Door controllers working from cached permissions during outages
- Remote revocation for phones, instant deactivation for lost cards
- Standard, replaceable hardware over proprietary lock-in
- Membership changes flowing into permissions without manual steps
Challenges that slow access projects down
Hardware surprises are the usual delay. Old doors, fire regulations, and landlord permissions all constrain what can be installed, and a survey that misses them produces change orders mid-installation. A thorough door survey, including fire and building regulations, belongs at the very start, with the landlord involved where the building is leased.
Permission creep is the second trap. Temporary grants that never expire, ex-members whose cards still work, and staff doors left open for convenience all accumulate. Regular access reviews — who has which permissions, and do they still need them — plus automatic expiry for temporary grants, keep the system honest.
- Thorough door survey including fire rules and landlord permissions
- Regular access reviews for stale permissions
- Automatic expiry for temporary and guest grants
- Fault alerts reaching staff before members report lockouts
Who it is for, and where it stops
This project fits coworking spaces with 24-hour access, multiple zones, or enough members that keys and shared codes no longer work safely. A small daytime-only space with staff always present may manage with simpler locks. Daily users are members entering, guests with temporary access, and staff managing permissions and logs.
It does not replace member management or booking, though it must sync with both. Budget and schedule depend on door count, hardware choice, and building constraints — confirm both with a quote before committing.
- Fits spaces with 24-hour access, zones, or larger member counts
- Daily users: members, guests, staff managing permissions
- Does not replace member or booking systems; it syncs with both
- Small daytime-only staffed spaces may suit simpler locks
Frequently asked questions
What keyless methods can members use?
Cards, phones, and codes are common, sometimes combined. The choice depends on the building, the hardware, and member habits. Whatever the method, credentials must be revocable when a member leaves.
Do doors work if the internet fails?
Yes, if controllers cache permissions locally. A network outage should not lock members out or leave doors unsecured; cached rules keep doors working until connectivity returns.
How do guests enter for a meeting?
Through temporary access granted by the host member or staff — a timed code, a guest credential, or a staff-escorted entry — that expires after the meeting.
What happens when a member leaves?
Access ends with membership, automatically, through the member-system link. Temporary grants and cards are deactivated, and the change is logged.
Are entry logs private?
Entry logs are personal data with retention rules and role-based access. Members can see their own access rights; staff review logs for incidents under defined procedures.