BEFORE YOU DEPLOY
Frequently asked questions.
A clear starting point for deployment, access control and your AdmitLayer subscription.
Getting started
How does a reviewed Ethernet Port Profile work with quarantine?
On an eligible, verified dedicated endpoint port, AdmitLayer preserves the original settings. With the required review and consent, quarantine detaches the profile from that port only, selects native VLAN 999 and blocks tagged VLANs. Restoration reapplies the saved port settings and profile assignment. The shared profile is unchanged. Uplinks, infrastructure, administrator and shared ports remain protected; actual device and firmware support must be verified.
Does quarantine automatically follow a device between Ethernet ports and Wi-Fi?
Automatic device mobility is not shipped in the current release. Wired actions use an explicitly reviewed binding. Cross-interface identity and session enforcement require additional verified adapters and ownership protections. The public demo does not represent that development prototype as a working product feature.
Why can a port VLAN and the last reported client VLAN differ?
Port-configuration readback and client telemetry are separate evidence. A client can retain an older reported VLAN after a port changes, especially without a fresh address/session update. AdmitLayer displays port configuration, client telemetry and independent connectivity verification separately. Selecting VLAN 999 alone does not prove every traffic path is isolated.
What does AdmitLayer do?
AdmitLayer brings device discovery, inventory, access reviews, policies and event logging into a Windows-hosted management console. Administrators can review devices and configure supported access-control workflows from one workspace.
Can I try it before deploying?
Yes. The interactive demo uses fictional devices and browser-local sample data. You can explore workflows without connecting network equipment. It makes no real network changes; do not enter passwords, API keys or other secrets.
Where is AdmitLayer installed?
The customer application runs on a Windows server using its bundled Node.js runtime and a dedicated Windows service. Installation, server resources, HTTPS and network access should be reviewed for your environment. The inquiry page is the place to discuss deployment requirements.
How is the application licensed?
Licensing is per production installation, bound to that installation’s identity and host. Admins, Operators and Viewers use the installation license; there is no separate user-seat license. See Pricing for current subscription information. Moving to another host requires an installation transfer.
Access and security
Does discovering a device automatically block its traffic?
No. Discovery and inventory provide visibility. Network enforcement requires supported equipment, configured adapters and explicit review. A policy decision in the console does not by itself prove that traffic has been blocked.
Which network equipment is supported?
Current supported UniFi workflows include inventory, selected guest-session management and reviewed wired-port control. Availability depends on the equipment, firmware and configuration. Cisco equipment profiles are placeholders in this release; Cisco management and enforcement are not available.
What do Emergency Port Shutdown and Restore Ports do?
Emergency Port Shutdown previews moving eligible, reviewed endpoint ports to isolation VLAN 999. It is not a blanket power-off of every switch port. Restore Ports previews returning recorded AdmitLayer changes to their original settings. Both require administrator review and confirmation; protected infrastructure ports are excluded. Isolation also depends on verified network rules.
Which sign-in options are available?
The application supports local accounts, Active Directory and Microsoft Entra ID when configured. Production setup requires customer SMTP delivery and account email verification, with supported authenticator options available afterward. Directory and mail integration must be configured and validated in your environment.
Deployment and support
Is Microsoft SQL Server required?
No. Local application storage is available. SQL Server is optional for primary application storage or reporting, with a reviewed migration workflow. AdmitLayer does not install the SQL Server engine or create SQL logins; the database connection and required permissions must be prepared separately.
Will an update preserve my application data?
The verified update workflow is designed to preserve the installation’s shared data and identity. Back up the installation first, verify the package checksum, and follow the supplied deployment instructions. Keep the prior verified release for rollback. Do not copy an unrelated fresh installation over existing customer data.
What support comes with a subscription?
The current subscription offering includes 24×7 technical support and free implementation support for the first 30 days of an active subscription. See Pricing for the current offering, or send an inquiry to discuss your environment.
Can I purchase a subscription on the website?
Online purchasing is not available yet. Use the inquiry form to discuss a subscription or implementation. Existing customers can use Customer login for the configured customer portal.
Have another question?
Tell us about your environment, or explore the console with fictional sample devices.
