In a multi-tenant office building, the same entrance serves employees, visitors and suppliers from several companies. One tenant's expectation of immediate admission may conflict with another's access requirements. Commissioning security for an Istanbul business centre should therefore start with decisions and workflows for shared spaces, rather than general claims about risks across the city.
Separate building management and tenant responsibilities
Security in common areas, visitor approval for a tenant's office and management of technical systems are different responsibilities. Who approves a visitor, who determines the permitted floor and what happens when the host cannot be reached? If answers vary by tenant, officers need a current and usable set of instructions.
NPSA's shared-workspace guidance discusses balancing openness with access control according to business needs. Although it is not Turkish law, the approach can help distinguish building-wide rules from tenant-specific permissions at a shared reception desk.
Investigate peak-hour delays before adding equipment
A morning queue may be caused by a reader fault, forgotten passes, visitor approval or deliveries arriving at the same point. Observe where waiting occurs before selecting a solution. Consider clear directions for employees and visitors, accessible routes and a separate way to handle exceptions without stopping the entire queue.
Screening arrangements must remain within applicable permissions and duties. A speed target does not expand an officer's powers, while invoking security does not by itself justify unnecessary delay. Test a proposed arrangement at busy times and with different user needs.
Connect delivery and parking procedures
Identify where couriers wait, who accepts a delivery and when an escort is required. An officer receiving a parcel should not automatically be regarded as certifying its contents or commercial acceptance. Large deliveries and out-of-hours office moves may require prior notification and explicit approval.
A vehicle registration appearing in a parking system does not authorise everyone inside the vehicle to access every floor. Vehicle admission and individual access permissions need separate consideration. Define the purpose, access restrictions and retention arrangements for plate and visitor records.
Make technical responsibilities explicit
Lift permissions, access cards, cameras and door alarms may work together, but the actual integration should be tested. Viewing an alarm is different from changing system settings or repairing a lift. Officers should know who maintains the systems and how to contact support outside normal hours.
Daily access convenience must not compromise emergency exits. NPSA's building-entry guidance considers reception, emergency exits and goods areas together. Applicable Turkish fire and building requirements still need assessment by the authorised technical professionals.
Review privacy and the quality of issue resolution
One tenant's visitor list should not be freely available to other tenants. Address privacy notices, necessary data fields and requests for records from the start. Visitor identification documents or CCTV recordings should not routinely circulate on personal phones.
Monthly reviews can consider bottlenecks, pending approvals, recurring equipment faults and communication complaints together. Instead of assuming that a provider has a particular control centre or technical platform, request a building-specific duty plan and a clear method for checking whether it works. The useful outcome is consistent access management across the shared building.
