> For the complete documentation index, see [llms.txt](https://docs.request.biz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.request.biz/administrator-guide/security/settings.md).

# Settings

The **Security > Settings** section allows you to customize security specific aspects:

<div align="left"><figure><img src="https://2723114352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaBzbSV4obl284TJgE1Hg%2Fuploads%2Fs7AumYFadUfOxiU6Zcif%2Fimage.png?alt=media&amp;token=9d9505c1-4753-4298-ae5e-e2ed33c84827" alt="" width="563"><figcaption></figcaption></figure></div>

## Email Whitelist

Here you can define a white list of domain names that are allowed to register themselves for the user frontend. You can enter several domain names by separating them with either a space, a comma or a semicolon.

If a user tries to register using an email with a different domain they receive an error and can't finish the registration.

## Local Authentication

The Local Authentication setting allows you to enable/disable the ability for users to register and log in to the application without any external tools. This is useful, for example, in cases where you prefer to only use external authentication (optionally with automatic user role assignment).

Disabling the option will remove the *register* and *sign in* options from the start screen of the user frontend.&#x20;

Note that disabling the setting does not actively log out users who are already authenticated locally. These users will remain logged in until their session expires or they log out manually. Once logged out, they will no longer be able to sign in while the setting is disabled.

Administrators will still be able to log in to the user application via the admin login. The top right corner ‘admin’ menu includes an option to navigate from there to REQUEST™.

{% hint style="danger" %}
NOTE: If you disable both Local and External authentication at the same time, regular users will have no way to sign in to the REQUEST™ application at all.
{% endhint %}

## External Authentication

<code class="expression">space.vars.PRODUCT\_NAME</code> can be integrated with external identity management systems for single sign-on scenarios. Currently, Microsoft authentication is supported using one of the following identity providers:

* [Microsoft Entra ID (MEID)](/administrator-guide/security/settings/microsoft-entra-id-meid.md)
* [Active Directory Federation Services (ADFS)](/administrator-guide/security/settings/active-directory-federation-services-adfs.md)

## Agent Client Access <a href="#agent_client_access" id="agent_client_access"></a>

For integration with on-premise services the system provides an [agent](/administrator-guide/integrations/agents.md) that can be installed in your local environment. The client secret shown in the section is unique for your environment and needs to be entered when the agent is configured.&#x20;