> For the complete documentation index, see [llms.txt](https://docs.inverse.watch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inverse.watch/admin-and-dev-guide/users/authentication-options.md).

# Authentication Options

### 1. Authentication Settings

Authentication options are configured through a mix of UI and Environment variables. To make changes in the UI visit the **Settings > General** tab.

{% hint style="info" %}
Only admins can view and change authentication settings. Some authentication options will not appear in the UI until the corresponding environment variables have been set.
{% endhint %}

### 2. Password Login

By default, the application authenticates users with an email address and password. This is called *Password Login* on the **Settings > General** tab. After you enable an alternative authentication method you can disable password login.

{% hint style="info" %}
The application stores hashes of user passwords that were created through its default password configuration. The first time a user authenticates through SAML or Google Login, a user record is created but no password hash is stored. This is called Just-in-Time (JIT) provisioning. These users can *only* log-in through the third-party authentication service.

If you use Password Login and subsequently enable Google OAuth or SAML 2.0, it’s possible that a user with one email address has two passwords to log-in: their Google or SAML password, and their original password.

We recommend disabling Password Login if all users are expected to authenticate through Google OAuth or SAML as it will reduce confusion.
{% endhint %}

###


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.inverse.watch/admin-and-dev-guide/users/authentication-options.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.