GHT: Glass House Technologies
GHT service / Physical security

Access control

Every opening knows who may pass, and when

Credentials, readers, controllers, locks, door contacts, request-to-exit devices, schedules, power, network, and administrator policy, with project-specific door-hardware and life-safety review.

What you should have at closeoutControlled openings with tested credential, schedule, door-position, power-loss, network-loss, and approved emergency behavior.
References3 reviewed
Last updated2026-08-20
Overview

What Access control includes

An access-controlled opening is more than a reader. It includes the door, frame, latch or lock, closer, hinges, power transfer, egress hardware, door contact, request-to-exit method, controller, power supply, network path, credentials, schedules, and event policy.

A qualified door-hardware and life-safety review may be required. The authority having jurisdiction, fire-alarm contractor, architect, or hardware specialist determines applicable requirements; an integrator should not replace that review with a generic wiring assumption.

Question to answer before designWho should enter each opening, when should access apply, and what must the door do during power, network, and emergency states?
Common situations

This service may fit when:

  • Keys are difficult to recover or audit
  • Door events do not match the physical state of the opening
  • Multiple credential systems create inconsistent access
  • New tenant, department, restricted area, elevator, or gate workflows
System components

What the system includes

A complete scope covers each part below and the connections between them.

01

Opening

Door, frame, lock, closer, egress, contact, request to exit

02

Field control

Reader, controller, supervised inputs, relays, protected power

03

Platform

Identity, credentials, groups, schedules, events, audit trail

04

Interfaces

Fire alarm, elevator, gate, intercom, video, visitor workflow

Project record

How site information becomes a tested project

A complete project record connects the conditions found on site, the design decisions made from them, and the tests and closeout documents delivered afterward.

Site information

What we confirm before design

  • Door, frame, hardware, egress, fire-rating, and accessibility conditions
  • Users, groups, schedules, credential issue and revocation workflow
  • Required behavior during power, network, fire-alarm, and lockdown states
Design decisions

What those findings determine

  • Credential: Choose from risk, population, issuance process, privacy, and offline behavior.
  • Reader link: Confirm controller, reader, topology, and commissioning support end to end.
  • Management: Evaluate connectivity, ownership, integrations, licensing, and recovery.
Closeout records

What you should receive

  • Door survey and function matrix
  • Hardware, power, pathway, network, and interface design
  • Credential groups, schedules, event rules, and administrator record

The exact inputs, decisions, and acceptance records depend on the site and signed scope.

Project stagesSurvey through closeoutView details
Project stages

How the work moves from survey to closeout

Each stage should produce the records and test results needed before the next stage begins.

  1. 01

    Survey the opening

    Document door and frame condition, hardware, egress, fire rating, power, pathway, network, accessibility, and current key or credential workflow.

    EvidenceDoor-by-door survey with hardware photos, measurements, existing conditions, and issues requiring specialist or authority review.
  2. 02

    Define states and policy

    Map authorized groups, schedules, lock and unlock behavior, forced or held events, power loss, network loss, emergency interface, and credential lifecycle.

    EvidenceDoor function matrix, credential and schedule matrix, riser, power budget, and interface responsibility list.
  3. 03

    Coordinate and implement

    Sequence locksmith, electrical, fire-alarm, network, and security work; install and label devices; then configure roles and event rules.

    EvidenceLabeled controller and field wiring, device inventory, configuration export, and coordination signoffs.
  4. 04

    Exercise every state

    Test valid and invalid credentials, schedules, door position, request to exit, forced and held events, power and network states, and approved emergency interfaces.

    EvidenceOpening-by-opening acceptance sheet, event-log samples, exception register, administrator accounts, and training record.
Design choicesCompare the available approachesView details
Options

How to choose the right approach

The right choice depends on the site, application, operating risk, and acceptance requirements. More equipment does not automatically improve the system.

FactorTypical approachMore demanding conditionsWhat determines the choice
CredentialTypical approach: Card or fobMore demanding conditions: Mobile, smart-card, PIN, or multi-factor optionsWhat determines the choice: Choose from risk, population, issuance process, privacy, and offline behavior.
Reader linkTypical approach: Legacy one-way reader signalingMore demanding conditions: Supervised bidirectional OSDP with Secure Channel where supportedWhat determines the choice: Confirm controller, reader, topology, and commissioning support end to end.
ManagementTypical approach: Local single-site administrationMore demanding conditions: Cloud or enterprise multi-site administrationWhat determines the choice: Evaluate connectivity, ownership, integrations, licensing, and recovery.
Door scopeTypical approach: Reader and lock onlyMore demanding conditions: Complete opening, power, egress, monitoring, and state validationWhat determines the choice: Do not price or approve a controlled opening from a reader count alone.
Before design

What we need to know

  • Door, frame, hardware, egress, fire-rating, and accessibility conditions
  • Users, groups, schedules, credential issue and revocation workflow
  • Required behavior during power, network, fire-alarm, and lockdown states
  • Available pathway, controller location, power, batteries, and network
  • Integration, event retention, reporting, and administrator requirements
At closeout

What you should receive

  • Door survey and function matrix
  • Hardware, power, pathway, network, and interface design
  • Credential groups, schedules, event rules, and administrator record
  • State-by-state acceptance results and event-log samples
  • As-built door schedule, labeled panels, asset list, and training
Equipment examplesSee relevant hardwareView details
Best fit

When this service makes sense

  • Organizations with frequent user or schedule changes
  • Sites that need event records and role-based administration
  • Openings that coordinate with video, visitor, elevator, or intercom workflows
  • Multi-site programs that need repeatable door standards
Before we commit

What we verify first

  • Door hardware, egress, accessibility, fire rating, and emergency release require project-specific review
  • Access control records entry events; they do not prove a person’s identity or prevent tailgating by themselves
  • Cloud administration and mobile credentials depend on licensing, supported devices, and connectivity
  • Existing doors may need locksmith, glazing, carpentry, electrical, or fire-alarm work outside the security scope
Site contextSee where this work is usedView details
Where it is used

How site conditions change the design

Occupancy, operating hours, user activity, regulation, weather, construction, and access can change the design.

Common questions

What people usually ask

Can existing locks and readers be reused?

Sometimes. Reuse depends on the condition and function of the opening, voltage and current, wiring, protocol, supervision, fail-safe or fail-secure behavior, egress, platform support, and acceptance testing.

What happens when the internet fails?

That depends on the controller architecture and cached policy. Offline credential decisions, schedules, event buffering, remote administration, and recovery should be documented and tested before acceptance.

Does access control replace a life-safety review?

No. Egress, fire-alarm interfaces, accessibility, rated openings, and local requirements need review by the responsible design professionals, trades, and authority having jurisdiction.

Standards and referencesReview the source materialView details