---
title: "Configure Password Requirements (Non-SSO)"
slug: "configure-password-requirements"
description: "Configure passwords requirements to enhance passwords security for accessing Gladly Team."
updated: 2026-05-19T19:51:37Z
published: 2026-05-19T19:51:37Z
canonical: "help.gladly.com/configure-password-requirements"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.gladly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Password Requirements (Non-SSO)

| **REQUIRED USER ROLE** Administrator | **PERMISSION OVERVIEW** [View permissions by role](https://help.gladly.com/docs/managing-users-and-roles#roles-and-responsibilities) |
| --- | --- |

For Gladly organizations that are unable to implement SSO, Password Requirements settings help strengthen access security for Gladly Team by allowing Administrators to enforce a minimum password length and set how often Agents are required to change their password.

## Access password requirements

1. Click ![](https://cdn.us.document360.io/7047b671-c4f2-4df0-bb0a-b9b511fd2452/Images/Documentation/hamburger-menu-icon(1).svg) on the top-left corner of the screen.
2. Click Settings.
3. Under **Security and Compliance**, click **Password Requirements**.
  - **Minimum Password Length –** Enter the minimum number of characters required for user Agent passwords. The default (and minimum) value is 8.
  - **Password Expiration Period –** Enter the number of days before Agents are required to change their password. Leave the field empty if you do not want passwords to expire.
    - **Note –**Leaving the Password Expiration Period field empty deactivate password expiration. Users will not be prompted to change their password which is not advisable.
4. Click **Save**.

Once saved, password requirements take effect for all users in your organization. Users will be prompted to update their password at their next login if the new requirements are not met.

Single Sign-On (SSO) allows users to access multiple applications and websites with one set of credentials. SSO uses a trust relationship between the IdP (Identity Provider and the SP (Service Provider). The IdP passes an assertion to the SP to authenticate the user, often using an identity standard like Security Assertion Markup Language (SAML) or OpenID Connect (OIDC).