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

# Getting Started with Windows Device Login

> Oloid's Windows login is a secure and user-friendly authentication method that allows Enterprise employees to log into Windows Laptops/Desktops/Servers, apps...

Oloid's Windows login is a secure and user-friendly authentication method that allows Enterprise employees to log into Windows Laptops/Desktops/Servers, apps, online services, and Workforce/HRMS Platform using physical identity factors (like Face, Badge, NFC tags, and Pin). The Physical Identity factors can be combined in any order using factor sequencing for Multi-factor Authentication.

This application is especially useful for factory workers, warehousing staff, supply chain operations, pharmacy chains, etc. where large number of employees use shared devices using shared credentials. These credentials are shared among all employees and even after the employee leaves remain the same. This creates security threat. With Oloid’s Passwordless solution for Windows, employees do not need to know Username and password, and their access is immediately deactivated, the day they leave. The access can be easily enabled on the day a new employee joins.

## Installation

* Download the Windows Device Login installer files
* Install the following Windows installer files.
  Pre-req ( DotNet SDK, C++ Redistributable)

For details refer to the following guides:

* [How to download Windows Device Login installer files](https://oloid.help/en/articles/8575199-how-to-download-windows-device-login-installer-files)
* [Windows Device Login Setup](https://oloid.help/en/articles/8624137-windows-device-login-setup)

## Configuration

### Initial set up

For Oloid's Windows login to function, it needs to be configured in the device (endpoint) and Oloid Platform.

### Platform

* Set up Application and Connection
* Create user and assign user to connection.

For setting up Application and Connection, see [Set up Application and Connection](https://oloid.help/en/articles/8585495-set-up-application-and-connection) guide

For creating User in Oloid Portal, see [User Onboarding](https://oloid.help/en/articles/8463554-user-onboarding) guide.

### Device

* Configuring Windows Device with Tenant , see **[Configuring Windows Device with Tenant](https://oloid.help/en/articles/8629775-configuring-windows-device-login-app-with-tenant)** guide
* Pairing Endpoint (Endpoint Creation)
  Endpoints are the devices that facilitate specific functionalities within an application. Each endpoint is associated with the application, and this association is commonly referred to as "pairing an endpoint."
  Pairing Windows Device involves associating endpoints with Passwordless application.
  An application is mapped to connections in the Oloid Platform. Pairing devices ensures that the right users within the mapped connections can effectively utilize the associated endpoint and application.
  Pairing an endpoint automatically creates endpoint ID in the Oloid portal and the endpoint details are added to the Endpoint section of Oloid Portal.
  For details see, [How to pair a Windows Device Login endpoint for Passwordless](https://oloid.help/en/articles/8512463-how-to-pair-a-windows-device-login-endpoint-for-passwordless)
* Enroll Badge from device. For detailed instructions , see **[How to enroll badge as credential using Windows Device Login App?](https://oloid.help/en/articles/8825186-how-to-enroll-badge-as-credential-using-windows-device-login-app)**

### Credential Set up

This is based on client requirements. Oloid's Windows login functions with a single factor (like Face, Badge, NFC tags, and Pin) or a combination of factors ( **Badge +Pin** and **NFC +Pin**).

Set up the following based on your need:

* Onboard User Faces. Refer [Face Onboarding](https://oloid.help/en/articles/8413861-face-onboarding) guide.
* Create Badges and assign it to users. Refer [Badge Onboarding](https://oloid.help/en/articles/8402155-badge-onboarding) guide.
* Create NFC and assign it to users. Refer [NFC Onboarding](https://oloid.help/en/articles/8600311-nfc-onboarding) guide.
* Create Pin and assign it to users. Refer [Pin Onboarding](https://oloid.help/en/articles/8408444-pin-onboarding) guide.
* Create Passwords ( Individual Domain and Individual Local). Refer [How to create Password for Windows Login](https://oloid.help/en/articles/8468581-how-to-create-password-for-windows-login) guide
* Create Shared Credentials (Shared Domain and Shared Local) and assign it to users. Refer [How to create Shared credentials and assign it to users](https://oloid.help/en/articles/8644776-how-to-create-shared-credentials-and-assign-it-to-users) guide.

## Multi-factor Authentication(MFA) Config

To enable Multi-factor Authentication (MFA) in Oloid's Windows login see [Factor Sequencing for Multi-factor authentication in Windows Device Login](https://oloid.help/en/articles/8408208-factor-sequencing-for-multi-factor-authentication-in-windows-device-login)

## SSO Login Config

To enable SSO Login in Oloid's Windows Device, see [How to Configure Windows Device Login app for SSO Login](https://oloid.help/en/articles/8564267-how-to-configure-windows-device-login-app-for-sso-login)

## Use

* [How to log into Windows Desktop/Laptop using face](https://oloid.help/en/articles/8637172-how-to-log-in-to-windows-device-using-face-through-windows-device-login-app).
* [How to login Windows Desktop/Laptop using badge](https://oloid.help/en/articles/8641938-how-to-log-in-to-windows-device-using-badge-through-windows-device-login-app)
* How to login Windows Desktop/Laptop using NFC and Pin ( coming soon)
* How to log into Windows Desktop/Laptop using face and auto-login into Workforce/HRMS application using SSO. ( coming soon)
* How to login Windows Desktop/Laptop using badge and Pin and auto-login into Workforce/HRMS application using SSO. ( coming soon)
* How to login Windows Desktop/Laptop using NFC and Pin and auto-login into Workforce/HRMS application using SSO. ( coming soon)
