> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-core/login-settings.md).

# Login Settings

* Available from IZ Suite Server **26.3.1**.
* In a multi-tenant installation each tenant has its own **`Login Settings`**

**`Login Settings`** controls what happens when a user signs in through single sign-on for the first time, and how long a session stays valid.

1. Navigate to **`Global Settings`** → **`Settings`**.
2. Search for **`Login Settings`** and click the **`Edit`** action.
3. Update the values described below and click **`Save`**.

| Key                           | Default | Description                                                                                                                                                                                                                                                            |
| ----------------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **`Auto Create New User`**    | `false` | When `true`, a user who authenticates successfully with **`Signin with CloudHub`**, **`Signin with Google`** or **`Microsoft Azure`** but does not yet exist in IZ Suite is created automatically. Does not apply to **`Signin with IZ Token`** or to security tokens. |
| **`Assign Roles`**            | empty   | Comma-separated ids of the roles granted to automatically created users. **Required when auto-create is enabled**: if it is empty, no user is created and the sign-in is rejected.                                                                                     |
| **`Session Timeout Seconds`** | `3600`  | Lifetime of a signed-in session in seconds. After this period the user must sign in again. Must be a positive whole number; invalid values fall back to one hour.                                                                                                      |
| **`Max Cache Entries`**       | `500`   | Reserved for future use.                                                                                                                                                                                                                                               |

| **`IZ User Auth Password Max Age`** | `90`    | Maximum age of an IZ User Auth password in days. A user whose password is older is asked to set a new one at the next sign-in. Replaces **`IZ Auth Token Max Age`**; an existing value is kept during the upgrade. |
| ----------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **`Max Failed Login Attempts`**     | `5`     | Number of consecutive wrong passwords or multi-factor codes after which the account is locked.                                                                                                                     |
| **`Account Lockout Minutes`**       | `15`    | How long a locked account stays locked.                                                                                                                                                                            |
| **`MFA Enabled`**                   | `false` | When `true`, users signing in with **`IZ User`** must enter a code from an authenticator app. Users without an authenticator enrol one at their next sign-in.                                                      |

### Automatic User Creation <a href="#automatic-user-creation" id="automatic-user-creation"></a>

Without automatic creation, every user must be invited first (see [Invite User](/product-guides/integral-zone/iz-suite/iz-core/organization/invite-user.md)); a user who signs in through SSO without an invitation is rejected.

With automatic creation:

1. The user signs in with one of the enabled single sign-on options.
2. IZ Suite looks for an enabled user with the same email address (case-insensitive).
3. If none exists, the user is created with the name and email from the identity provider and the roles listed in **`Assign Roles`** are granted.
4. The user is signed in immediately.

#### Finding Role Ids <a href="#finding-role-ids" id="finding-role-ids"></a>

1. Navigate to **`Organization`** → **`Roles`**.
2. Enable the **`Id`** column from the column settings.
3. Copy the ids of the roles to grant, for example a viewer role scoped to the organization new users should see, and enter them separated by commas in **`Assign Roles`**.

* Grant only the minimum roles needed. Anyone who can authenticate with the configured identity provider will receive these roles on first sign-in. Restrict the identity provider application to the intended users or groups (for example **`Who can use this application`** in an Anypoint Connected App, or user assignment in Microsoft Entra ID).
* Users created automatically appear under **`Organization`** → **`Users`** like invited users and can have roles, permissions and organizations adjusted afterwards

### Session Timeout <a href="#session-timeout" id="session-timeout"></a>

**`Session Timeout Seconds`** applies to sessions created after the setting is saved. Existing sessions keep the lifetime they were issued with. Security tokens generated under **`Organization`** → **`Tokens`** and agent sessions are not affected by this setting.

**`Sign Out`** ends the session immediately, regardless of the remaining lifetime.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-core/login-settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.