One Floor, Six Companies: Entry Management in Shared Office Suites

Six companies share one floor. Each has its own staff, its own hours, its own idea of what a locked door means. But there’s only one way in — and someone has to run it. Shared office suites, co-working floors and serviced commercial spaces strip away the assumption that a building has one organization behind its entrance.

This article is about the access structure for those spaces: how to arrange credentials so each tenant manages its own people, the operator doesn’t become a full-time doorman, and the entrance still behaves like one coherent building.

Start with what’s actually shared

The first decision isn’t technical — it’s deciding which access is common and which is private:

The common entrance is where nearly all the operational pain accumulates, because it’s the one place every departure, arrival and visitor policy meets. So the practical design sets the suite doors aside as the tenant’s business, and concentrates structure on the front.

Two structural models for the common entrance

Suites run one of two ways, and the choice determines the credential strategy:

1. Operator-managed. The building operator holds the access list and issues credentials to tenants, removing them when leases end. Clean and centrally controllable — and it means the operator’s team does the routine credential admin for everyone. This model suits smaller tenants and serviced offices where the operator already provides front-desk and reception services.
2. Tenant-administered. Each company holds an administrative credential for the common entrance’s management layer — its own people are its own list. The operator keeps override and facilities access. This model suits larger tenants who don’t want to submit a help ticket every time an employee joins.

Both are legitimate; what fails is the hybrid nobody chose: the operator with a master credential, tenants informally sharing it, and a front door whose actual access list exists only in people’s memories. Whichever model a building picks, the essential discipline is the same one households use — every person on their own credential — with the building as the scale at which that discipline pays off most.

Where shared-suite access goes wrong

• The shared front-door code. It leaks within weeks, and when it finally changes, it changes for everyone at once — including the tenant who did nothing wrong. The cost of one shared code is paid by every tenant’s access governance, and per-person credentials cost the same hardware money.
• The ghost freelancer. Hot-deskers come and go; the tenancy list is never as tidy as the business directory. The one-minute-per-person removal habit — the same one our visitor access guide describes for households — is what keeps the entrance list honest.
• The facilities exception that becomes permanent. A cleaner who came for one weekend, a contractor whose job ended, the delivery courier route — all legitimate reasons that quietly become standing credentials. The fix is the same everywhere: an expiry, planned at creation.
• The overnight gap. Suites often close the front desk at night but the building keeps working — that starts having access requirements the daytime model didn’t anticipate. Deciding the night story deliberately (who can enter after hours, with what credential, and whether the alarm or building security needs to know) prevents the improvised solutions people otherwise invent.

What the hardware needs to provide

The multi-tenant variant: co-working and hybrid floors

Full co-working spaces push the shared-entrance model further: the “tenant” may be an individual with a hot desk, and the access list changes by the week. The relevant hardware facts don’t change — capacity, per-user management, temporary access — but the process does. Successful co-working operations run credential issuance like a booking system: tied to a membership, expiring with it, renewable automatically. The lock’s job is only to honor a list someone else maintains; the maintenance discipline belongs to the operator’s business system, and the honest hardware requirement is a management layer that integrates with how that business already runs.

Common questions

Should tenants get the master credential for the common door?

Generally no — and the reason is maintenance, not trust. A master credential means every tenant can add or remove anyone, which makes the building’s access list impossible to reconstruct when questions arise. Tenant-administered access works better when it’s scoped: each tenant manages its own people’s credentials, and the operator retains override, not the tenants.

How do visitors and deliveries fit a shared entrance?

The shared version of the household problem: a courier needs in, a client is expected, and there’s no single household to call. The common solutions are a staffed reception (where the operator’s credential handles it), an intercom system tied to a temporary credential, or scheduled access windows. Whichever fits the building, the rule is the same: the visitor gets access to the entrance, not a copy of the tenant-level credential.

What about fire and emergency egress requirements?

Shared commercial premises are governed by local code, and egress requirements vary by jurisdiction: the practical step is confirming — in writing, per building — how the chosen lock’s egress behavior complies. This is the same principle as our rental operations guide: compliance is a per-property verification, not a claim any supplier should make on your behalf.