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

> ## Agent Instructions
> ### Authlete versions
> Authlete 3.0 is the current version. Unless the user says they use another version, answer for Authlete 3.0 using the 3.x documentation.
> Documentation for Authlete 2.x (pages under `/v2/` and `/ja/v2/`) is for the legacy version. Refer to it only when the user is on Authlete 2.x.
>
> ### Authlete architecture
> Authlete is a backend engine for OAuth 2.0 and OpenID Connect processing. End users and client applications do not call it directly; the service provider's authorization server and API server call Authlete's APIs. Authlete handles protocol processing and token, client, and service management, while the service provider owns the OAuth/OIDC endpoints and user authentication.
> See [Architecture](https://developers.authlete.com/get-started/introduction-to-authlete/architecture.md).
>
> ### Concepts
> If the user is new to Authlete, read these pages first:
> - [Request and Response](https://developers.authlete.com/get-started/concepts/request-and-response.md): Core API requests pass the client's request parameters as-is, and responses return `resultCode`, `action`, and `responseContent`.
> - [Action Handling](https://developers.authlete.com/get-started/concepts/action-handling.md): Branch on `action`, never on `resultCode`, and map each action to the HTTP response your server returns.
> - [Two-Step API Calls](https://developers.authlete.com/get-started/concepts/two-step-api-calls.md): Actions such as `INTERACTION` are completed with a second call (`/auth/authorization/issue` or `/auth/authorization/fail`) linked by a `ticket`.
> - [Management API Overview](https://developers.authlete.com/get-started/concepts/overview.md): The Management API configures services, manages clients, and operates issued tokens, separately from the protocol flows handled by the Core API.
> - [API Authentication](https://developers.authlete.com/get-started/concepts/authentication.md): Authlete APIs use bearer tokens: a Service Access Token (one service) or an Organization Token (the whole organization).

# Environment Settings

> Explains how Environment Admins control who can create organizations and manage every organization in the environment.

> [!NOTE]
>
> This article applies only to Self-Managed and Dedicated Cloud environments. The shared environment (Shared Cloud) is managed by Authlete and is out of scope for this document.

Environment Settings is available to Environment Admins and Platform Admins only. Its Organization Governance tab has two parts: the setting that controls who can create organizations, and the list of every organization in the environment. See [Delegated Admin](https://developers.authlete.com/configuration-reference/environment/delegated-admin.md) for an overview of the role.

## Environment Settings and All Organizations

Environment Settings is separate from the All Organizations page that every user sees. All Organizations lists only the organizations the signed-in user personally belongs to, and it works the same way for Environment Admins and Platform Admins as for everyone else. Environment-wide organization management happens in Environment Settings.

## Allowing or restricting organization creation

The Organization Creation Enabled setting controls who can create new organizations in the environment. It's turned on by default.

* When it's on, any user can create new organizations.
* When it's off, only Platform Admins and Environment Admins can create organizations, and the "Create Organization" action is hidden from everyone else.

When you change the setting, Console asks you to confirm with "Restrict Organization Creation?" or "Allow Organization Creation?". Existing organizations and their admins are not affected either way. Changes to this setting are recorded in [Audit Logs](https://developers.authlete.com/configuration-reference/environment/audit-logs.md).

## Managing organizations in the environment

This list shows every organization in the environment, including ones you aren't personally a member of, with each organization's name, ID, and billing plan. From here, Environment Admins and Platform Admins can:

* Rename an organization. Select the pencil icon next to its name, enter the new name, and select Save Changes. Renaming doesn't affect the organization ID or any existing integrations.
* Delete an organization. Select the delete icon in the Actions column, then confirm.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.