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

# Enable OloID Account for a Connection

> This document provides use-cases for when to enable OloID for a connection.

## Introduction

OloID account enablement is required only for specific authentication flows within the Tenant Admin Portal. Enabling OloID ensures that user identity is available for authentication scenarios that depend on user-level access.

This document helps admins determine when OloID must be enabled for a connection and when it is not required.

***

## OloID Enablement Reference

Use Case

OloID Required

Description

User Portal Login

Yes

Required for users to log in to the User Portal using OloID-based authentication

Vault Authentication (via Supervisor Session)

Yes

Required when using an active session from the Supervisor application to authenticate into Vault

WebKey Application

No

OloID is not required for WebKey-based authentication flows

Supervisor Application Usage

No

OloID is not required for standard Supervisor application operations

***

## Example Scenarios

### Connection A: User Portal Access

* **Use Case**: Employees log in to the User Portal to manage their profile and authentication settings.
* **Configuration**: OloID account must be enabled.
* **Reason**: The login flow requires user identity to authenticate and map actions to a specific user.

***

### Connection B: Vault Access via Supervisor Session

* **Use Case**: A supervisor authenticates into Vault using an active session.
* **Configuration**: OloID account must be enabled.
* **Reason**: The system uses the user’s identity from the session to authorize access.

***

### Connection C: WebKey Authentication

* **Use Case**: Users authenticate into applications using WebKey (badge, biometric, or device-based login).
* **Configuration**: OloID account is not required.
* **Reason**: Authentication is handled at the device or application level without relying on OloID identity.

***

### Connection D: Supervisor Application Usage

* **Use Case**: Admins or supervisors use the Supervisor application for monitoring or operations.
* **Configuration**: OloID account is not required.
* **Reason**: The application functions without requiring OloID-based user identity for authentication.