---
title: "Configure the user matching field for automatic login via GPO"
description: "Use a Signitic user field to identify users when the Windows username does not match the email address."
url: https://support.signitic.com/en/articles/9561124-configure-the-user-matching-field-for-automatic-login-via-gpo
collection: "Access & security"
updated: 2026-10-02
language: en
alternates: [fr, de, it, pt]
---

# Configure the user matching field for automatic login via GPO

Use a Signitic user field to identify users when the Windows username does not match the email address.

> **Info:** During a Signitic Agent deployment via GPO, automatic connection is based on the identifier sent by the desktop agent. By default, this identifier can be the Windows username or email address depending on the script used.

In some environments, Windows usernames do not correspond to users' email addresses or use a specific format. In this case, you can store this identifier in a Signitic user field, then instruct the Signitic Agent which field to use to find the correct user.

## When to use this option

-   The Windows username does not correspond to the user's email address.
    
-   The username format is specific to your organization.
    
-   Automatic connection via GPO does not correctly find some users.
    
-   You wish to continue sending the username from the GPO script, but match it to a dedicated Signitic field.
    

## Operating principle

The GPO script sends a user identifier to Signitic during the creation of the desktop agent configuration file.

Signitic then compares this identifier with the field defined in the **Signitic Agent** connector. If the value sent by the agent matches the value present on a Signitic user, the agent can automatically connect the correct user.

By default, matching can be performed on the **Email**. If your users have specific usernames, select instead the additional field where you have imported or specified this username.

## Before you begin

-   The selected field must be populated in the relevant Signitic users.
    
-   The field value must match exactly the identifier sent by the GPO script.
    

## Configure the matching field

1.  Open **Settings** in Signitic.
    
2.  Go to **Connectors**.
    
3.  Open the **Signitic Agent** connector.
    
4.  In the **Settings** tab, locate the **User Matching Field** field.
    
5.  Select **Email** or the **custom field** that contains the username to be used.
    
6.  Save the configuration.
    

![](https://staticfiles.gleap.io/gattachments/0dgdXq0Dghk2qa0BfqNZtZmg1cGkcU6g6FC4AmZGgmk12W6o54ytbXT3sMB7VLsnWpu6ttx3bDp.png)

## Example

If the GPO script sends the Windows username `jdupont`, but the Signitic user has the email `jean.dupont@entreprise.com`, email matching is not sufficient.

In this case, enter \`jdupont\` in an additional user field, for example **Additional Field #1**, then select the same field in the **Agent Signitic** connector.

## Checkpoints

-   Verify that each affected user has a unique value in the selected field.
    
-   Avoid spaces, case differences, or variations between the username sent by GPO and the value stored in Signitic.
    
-   If multiple users have the same value, automatic login may not direct the correct user.
    
-   After making changes, restart a session or redistribute the agent configuration to test automatic login.
    

## Frequently Asked Questions

Can I keep email as the matching field?

Yes, if the identifier sent by the GPO script matches the user's email address.

Which field should I choose if my usernames are different from emails?

Select the additional field where the username used by the Windows environment has been imported or entered.

Must the value be identical to the Windows username?

Yes. The value stored in Signitic must correspond to the identifier actually sent by the desktop agent.