> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/authentication/admin-portal/settings/general-settings.md).

# General Settings

The page has two tabs — Preferred User Stores and Self Registration — plus tenant information and session controls.

***

### Overview

The control center for your tenant's basics. From **Settings > General**, tenant and community administrators can view core tenant details (tenant name and community name), set how long sessions stay active, choose where users are looked up, and decide whether people can sign themselves up.

To get there: log in to your tenant as a community administrator and navigate to **Settings > General**.

### Preferred user stores

Designate which directories 1Kosmos searches when a user signs in. When a user enters a username or scans a QR code, the system searches the **database** first, then your **Primary**, **Secondary**, and **Tertiary** stores in order. New registrations are added to the database. You can select up to three user stores.

{% hint style="info" icon="lightbulb-exclamation-on" %}
**Important:** If you've integrated an Active Directory (AD) but haven't set it as a preferred user store, users from that directory won't be able to log in.
{% endhint %}

{% hint style="info" %}
**Tip:** User directories must be created and configured *before* you set them as preferred user stores. See [Connect to AD via Broker,](/authentication/authentication-broker/connect-directory-via-the-adminx-broker.md) [Connect to LDAP via Broker](/authentication/authentication-broker/connect-to-ldap-via-broker.md), [Connect to LDAP](/authentication/authentication-proxy/ldap-setup.md), and [Connect to Azure AD.](broken://pages/WI8GAcas8tOTSdJijaoX)
{% endhint %}

**Set a preferred user store:**

1. In the **Preferred User Stores** section, click the **pencil** icon on the **Primary** row.
2. Select a directory from the drop-down (populated from directories linked to your tenant) and click **Save**.
3. Repeat for your **Secondary** and **Tertiary** stores if needed.

**Remove a preferred user store:**

1. Find the store you want to remove and click the **trash** icon on its row.
2. Click **Continue**.

{% hint style="warning" %}
**Caution:** User accounts from a removed user store will no longer be able to log in.
{% endhint %}

### Tenant information & session age

This section shows your tenant and community information and lets you set the maximum session duration.

**Max Session Age** determines how long a session stays active before users are automatically logged out and redirected to the sign-in page.

1. In the **Max Session Age** field, click the **pencil** icon next to the listed minutes.
2. Enter a new maximum session age **in minutes**.
3. Click **Save**.

### Self-registration

Decide whether users can create their own account and onboard themselves from the sign-in page — useful or not depending on your organization's security policies.

1. On the **General Settings** page, click the **Self-Registration** tab.
2. Turn the **Self register users** slider **ON** to allow self-registration, or **OFF** to disable it.
3. Click **Save**.


---

# 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://docs.1kosmos.com/authentication/admin-portal/settings/general-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.