---
title: "Built-in User Management"
slug: "built-in-user-management"
updated: 2026-05-06T19:23:50Z
published: 2026-05-06T19:23:50Z
canonical: "help.hyperscience.ai/built-in-user-management"
---

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

# Built-in User Management

The setup of our built-in user management system depends on what kind of Hyperscience instance you are using.

After initial setup, you can add users to our built-in user management system by following the steps outlined for your version of Hyperscience ( [v38](/v38/docs/adding-editing-and-deactivating-users) | [v39](/v39/docs/adding-editing-and-deactivating-users) | [v40](/v40/docs/adding-editing-and-deactivating-users) | [v41](/v41/docs/adding-editing-and-deactivating-users) | [v42](/v42/docs/adding-editing-and-deactivating-users) | [v43](/v43/docs/adding-editing-and-deactivating-users) ).

## On-premise / private cloud instances

To use the Hyperscience built-in user management system, you must define the initial admin user and password in the “.env” file (for Docker/Podman-based deployments) or the respective section of the Helm chart’s `values.yaml` (for Kubernetes-based deployments; see [Helm Chart](/deployment/docs/helm-chart#postinstallation-steps-development-only) for more information):

```plaintext
FORMS_USER=<username>
FORMS_PASS=<password>
```

> [!NOTE]
> In v32 and later, you can choose to store your system-level credentials in a secrets manager. To learn more about our secrets-management integration, see [Secrets Management](/deployment/docs/secrets-management).

## SaaS instances

Hyperscience uses Okta to manage users in SaaS instances. Okta authentication is enabled by default.

For more details, contact your Hyperscience representative.