# Application Authentication and Permissions

We support the following authentication methods:

- **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.

- **LDAP**: LDAP (Lightweight Directory Access Protocol) is a protocol used to access and manage directory information. It’s applied for centralized authentication and stores information about users and groups. It allows for single sign-on across multiple applications.

- **OpenID Connect (OIDC)**: The steps required to set up OpenID Connect (OIDC) depend on what kind of Hyperscience instance you are using. On-premise/private cloud instances require creating an application configuration for Hyperscience.

- **SAML**: SAML (Security Assertion Markup Language) is an open standard that allows identity providers (IdPs) to pass authorization credentials to service providers (SPs) via transactions that use XML for communication.

- **SAML Configuration in Azure**: These instructions explain how to configure Hyperscience to use an Azure application as an identity provider.

- **External Authentication Methods and API Users**: In v27.0.8+, v28.0.10+, v28.2.3+, and v30+, the system will verify that only one of the authentication methods is enabled if an external authentication provider is activated.

- **Permissions Variables**: This article describes permissions-related ".env" variables that we support.

- **Machine to Machine (M2M) Authentication with OAuth 2.0**: Machine-to-machine authentication is required for SaaS deployments of all versions and strongly recommended for on-premise deployments of Hyperscience v40 and later.