Office buildings
Control employee and visitor entry within organizational policies.
Security and access
Security GateClearer entry. More controlled access.
Knowing who is entering and whether they have permission matters at organizational entrances. Liyan Security Gate is introduced for entry and access control, event recording and integration with identity systems around your site and operating rules.
Bring an example of your team’s actual work to evaluate the product.
From entry request to event recordA conceptual workflow
Entry request
Review the person within the defined entry flow
Access control
Apply organizational rules and permissions
Event record
Entry information for operational follow-up
Security Gate · Security and access
Enterprise use cases
For sites with defined entry flows
Assess the solution around visitors and site rules, from employee entry to guest arrivals.
Industrial and operational sites
Review entry rules for working areas alongside site operations teams.
Service locations
Align visitor entry with identity information and service permissions.
Core capabilities
Entry control with information you can follow
An entry solution should fit access policies and actual site conditions. Review visitor scenarios before selecting implementation methods.
Entry and access control
Manage entry around defined organizational rules. Users, entrances and control methods are established during requirements analysis.
For applying entry rulesEvent recording
Record entry events for operational follow-up. Required information, viewing permissions and use of records are reviewed with the responsible team.
For reviewing entrance activityIdentity system connections
Coordinate with user information and identity systems. Feasibility and permission exchange methods depend on existing system structures.
For aligned identity and accessSetup readiness
Deployment and integration: what to prepare
Clarify these points before starting to define setup scope and responsibilities.
Site and equipment
Identify entrances, site conditions and existing equipment. Identification methods and compatible equipment are specified in the implementation proposal.
Entry rules
Define separate rules for staff, guests and people without access. Assign responsibility for exceptions.
Integration and outages
Identify the source of user and permission information. Record outage and emergency behavior in the operational plan before implementation.
Frequently asked questions
What does Security Gate do?
The solution is introduced for entry and access control, event recording and connections to organizational identity systems. Implementation details are assessed around your site.
Which equipment or identification methods are used?
Equipment, identification methods and compatibility with existing facilities need confirmation during technical review. Site conditions and access policies guide selection.
Can it connect to our current system?
Identity system integration is a core area of the solution. Feasibility and exchange methods are established after reviewing interfaces and existing system structures.
What happens if a connection fails?
Disruption behavior, emergency conditions and decision responsibilities should be defined before operation. Review policies with the operations team and site managers.
How is implementation cost determined?
Entrances, site conditions, equipment, integrations, installation and support determine scope and cost. Share your site requirements with Liyan.
Getting started
Start with a real scenario
Choose an entrance and several entry scenarios to review the technical and operational requirements of that site.
Review the site and rules
Define entrances, users, operating hours and site conditions.
Explore access scenarios
Review permitted entry, denied access, guests and disruption scenarios.
Define deployment requirements
Discuss equipment, integrations, installation, support and scope.
Review your site’s entry workflow.
Share your site conditions and access rules to explore a suitable entry control solution.