Feature Overview: Security and Access Control
Lanview security and access control covers operator accounts, roles, permissions, authentication, two-factor authentication and device trust.
Lanview Server enforces security decisions. Studio may hide or disable controls based on permissions, but Lanview checks permissions when actions are requested.
What this feature area includes
Security and access control includes:
- Security users.
- Role assignment.
- Role-based permissions.
- permission checks.
- Two-factor authentication.
- Password and account management.
- Device approval.
- Client identity and trust policy.
- Device reassociation for rebuild or replacement scenarios.
What it is not
Lanview security users are not Windows domain users unless a specific integration is separately documented.
For device trust, describe administrator-visible policy and outcomes rather than implementation details.
Where to find it
Security features appear in:
- Studio > Security.
- Authentication, two-factor authentication and Client identity settings where exposed in Studio.
- Device approval processes.
- Device Window settings for device-level identity actions where exposed.
- AdminConsole or local console for bootstrap and emergency recovery where appropriate.
Permissions and access
Important permission areas include:
- Viewing and managing security users.
- Viewing and managing roles.
- Security module access.
- Device approval and reassociation.
- Server settings management.
- Feature-specific permissions for each administrative area.
Role design should avoid shared operator accounts and should assign powerful permissions only where needed.
Policy and settings
Security state is managed by Lanview Server. Server-level security settings include authentication mode, two-factor authentication mode and Client identity rollout mode.
Roles and permissions affect Studio, Server interfaces and console surfaces.
Audit behaviour
Lanview audits login events, permission denials, security user changes, role changes, password resets, two-factor authentication events, Client identity events and sensitive device trust actions where catalogued.
Many security administration actions can require an operator reason.