Skip to main content
Version: 5.0 🚧

Authorization settings

Overview​

Use the Authorization settings page to control authentication behavior for customer and installer access.

Use this page when you need to:

  • Control verification-code expiration.
  • Set login attempt limits and lock timeouts for account and panel access.
  • Configure permanent user behavior for panel access.

These settings help reduce brute-force and replay risk while keeping access practical for authorized users.

Before you begin​

Required permissions​

  • You must have permission for the Interactive category in Server Settings.

Preconditions​

  • The Interactive category of Server Settings section is available to your role.
  • You understand your organization's policy for session lifetime, retry limits, and lockouts.

Important limitations​

warning
  • Saving any change restarts the session-manager-related service, which clears in-memory lock state and permanent-user state.
  • If a value is too strict, legitimate users can be locked out more often.
  • If a value is too permissive, brute-force and replay exposure increases.

Page layout​

Authorization settings dialog​

info

The Authorization settings dialog is shown as separate screenshots by section. Use the tabs below to view each part of the dialog.

Factor & code settings (light)Factor & code settings (dark)
CalloutUI elementDescriptionWhen to use
1First factor expiration period, secondsSets the lifetime of the first-factor token issued after customer account login. Applies to the ConnectAlarm app. Accepted values: 10-100000 seconds.Use to control idle session duration in the ConnectAlarm app.
2Email code expiration period for applications, secondsSets how long email verification or registration codes remain valid. Applies to ConnectAlarm and AlarmInstall apps. Accepted values: 30-65535 seconds.Use to limit replay risk from delayed or intercepted email codes.
3Email code length for Installer appSets the code length for installer email verification flows. Applies to the AlarmInstall app. Accepted values: 5-72 digits.Use when tuning security and usability for installer onboarding.

How to use this page​

Configure first and second factor token expiration​

Goal:

  • Set how long first-factor and second-factor sessions remain valid.

Steps:

  1. Open Settings and go to Authorization settings.
  2. Select the edit icon.
  3. Enter the required value for First factor expiration period, seconds.
  4. Enter the required value for Second factor expiration period, seconds.
  5. Select Save.

Expected result:

  • New first-factor and second-factor expiration periods apply to subsequent sessions.

Configure email verification code behavior​

Goal:

  • Define expiration and strength of email verification codes.

Steps:

  1. Open the Authorization settings edit dialog.
  2. Set Email code expiration period for applications, seconds.
  3. Set Email code length for Installer app.
  4. Select Save.

Expected result:

  • Installer and customer verification flows use the updated email-code expiration.
  • Installer verification flows use the updated code length.

Configure account login lockout policy​

Goal:

  • Reduce repeated password guessing against customer accounts.

Steps:

  1. Open the Authorization settings edit dialog.
  2. Set Account login attempts limit.
  3. Set Account login lock timeout, seconds.
  4. Select Save.

Expected result:

  • Customer account logins are blocked for the configured timeout after repeated failed attempts.

Configure permanent user lifetime​

Goal:

  • Define how long recently authenticated customer users keep permanent-user status for a panel.

Steps:

  1. Open the Authorization settings edit dialog.
  2. Set Permanent user lifetime, days.
  3. Select Save.

Expected result:

  • Customers who successfully logged into a panel keep permanent-user status for the configured number of days.
note

Default value for Permanent user lifetime, days is 1 day.

Tips​

tip
  • Record current values before you edit this page.
  • Change lock-related values during a planned window because saving restarts the session-manager-related service.
  • Keep account and panel lockout settings aligned with your incident-response policy.
  • Use shorter token lifetimes for higher-security environments and longer lifetimes for operations that require extended sessions.

Troubleshooting​

Too many temporary account lockouts​

Possible causes

  • Account login attempts limit is too low.
  • Account login lock timeout, seconds is too high.

What to do

  1. Review account login limit and lock timeout settings.
  2. Increase attempt limit or reduce lock timeout if policy allows.
  3. Save and monitor lockout events.

Verification email code is rejected​

Possible causes

  • Email code expiration period for applications, seconds is too short.
  • User entered an old code after it expired.

What to do

  1. Request a new verification code.
  2. Enter the new code before expiration.
  3. Increase the email code expiration period if policy allows it and delivery latency requires it.
Was this page helpful?