---
locale: "en"
updated_at: "2025-10-28T15:22:36.154Z"
canonical: "https://www.isdecisions.com/en/userlock/docs/reference/server-settings/advanced-settings"
---

# Advanced settings

Deep configuration for support or advanced administration.

> **Note**
>
> - To access this page, go to **Server settings ▸ Advanced settings**.
> - You need at least *read* [permission](/userlock/docs/reference/server-settings/permissions) on Server settings to view this page.

## What advanced settings cover

Advanced settings are **not designed for day-to-day administration**.

They exist mainly to solve edge cases such as troubleshooting, custom integrations, or very specific environments. In most deployments, they should remain at their default values.

Parameters are grouped into the following categories in the interface:

- **Multi-Factor Authentication**: code synchronization, VPN challenge, push notifications, IIS compatibility, enrollment rules.
- **General**: database and cleanup rules, logging, Active Directory queries, license notifications, deadlock handling.
- **Agents**: communication methods, deployment options, inclusion/exclusion lists, macOS support.
- **Access policies**: restriction behavior on unlock, IP ranges (inside/outside), session counting exceptions.

Each parameter includes inline documentation in the interface with default values, allowed ranges, and recommendations.

> **Important**
>
> - ⚠️ **Do not modify these settings** unless explicitly instructed by IS Decisions support, or unless a documented use case requires it.
> - Some changes require a restart of the UserLock service to take effect.

## Risks of misconfiguration

Changing advanced settings without guidance can:

- reduce performance by overloading the server or agents,
- create security gaps (e.g., disabling encryption or MFA enforcement),
- cause service instability or unexpected session resets.

## Best practices

- Always consult support before changing a parameter you don’t fully understand.
- Test changes in a non-production environment when possible.
- Document your changes (date, reason, expected impact) to simplify troubleshooting.
- Revert quickly if unexpected behavior occurs.