Login Identifier Settings determine how users identify themselves when signing in to Fixiam.

A login identifier is the unique value a user enters during authentication before providing their password or completing additional verification steps.

Organizations can configure which identifiers users are allowed to use when signing in.

Accessing Login Identifier Settings

Navigate to:

Settings → Login Identifier Settings

>

Understanding Login Identifiers

A login identifier uniquely identifies a user account.

Fixiam supports the following login identifiers:

Administrators can select up to two login identifiers.

Why Login Identifiers Matter

Login Identifiers affect several areas of the platform.

They determine:

• How users sign in
• Required user creation fields
• Required bulk import fields
• User onboarding requirements

Example

Configuration:

Work Email
Employee ID

Users may authenticate using:

[email protected]

or

EMP10254

Configuring Login Identifiers

To configure login identifiers:

1. Navigate to Login Identifier Settings.
2. Select the desired identifiers.
3. Save the configuration.

Screenshot Placeholder

Insert Login Identifier selection screen.

Supported Configurations

Work Email Only

Recommended for most organizations.

Example:

[email protected]

Benefits:

• Easy for users to remember
• Common enterprise standard
• Simplifies onboarding

Employee ID Only

Often used in organizations where employee numbers are the primary identity source.

Example:

EMP10025

Benefits:

• Consistent internal identifier
• Independent of email changes

Work Email and Employee ID

Recommended for larger organizations.

Example:

[email protected]

or

EMP10025

Benefits:

• Greater flexibility
• Alternative login method available

Impact on User Creation

Selected login identifiers become required fields during user creation.

Example

Configured Login Identifier:

Work Email

Result:

Work Email = Required

Example

Configured Login Identifiers:

Work Email
Employee ID

Result:

Work Email = Required

Employee ID = Required

Impact on Bulk User Import

Login Identifier Settings also affect user import templates.

Any configured login identifier must be present in uploaded files.

Example

Configured Login Identifier:

Work Email

Required column:

work_email

Example

Configured Login Identifiers:

Work Email
Employee ID

Required columns:

work_email
employee_id

Missing required identifiers may cause validation errors during import.

Impact on User Authentication

During sign in, users may enter any enabled login identifier.

Example

Configured Login Identifiers:

Work Email
Employee ID

The following are valid:

[email protected]

EMP20452

Both identify the same user account.

Best Practices

Small Organizations

Recommended:

Work Email

This provides the simplest sign in experience.

Medium to Large Organizations

Recommended:

Work Email
Employee ID

Provides flexibility and supports operational scenarios where employees may not know their email credentials.

Enterprise Environments

Use identifiers that already exist within your authoritative identity source.

Examples:

• Active Directory
• Microsoft Entra ID
• Google Workspace
• HR Systems

This helps maintain consistency across systems.

Troubleshooting

User Cannot Sign In Using Employee ID

Verify:

• Employee ID is enabled as a Login Identifier.
• Employee ID is populated on the user's profile.
• The correct value is being entered.

User Creation Form Requires Unexpected Fields

Verify:

• Login Identifier configuration.
• Required identifier settings.
• User creation form configuration.

Bulk Import Validation Errors

Verify:

• Required identifier columns exist.
• Values are unique.
• Values are populated for all users.

Users Are Unsure Which Identifier to Use

Communicate the approved sign in methods during onboarding and enrollment.

Related Topics

• Users Overview
• Creating Users
• Bulk User Creation
• User Synchronization
• Password Authentication
• Multi Factor Authentication (MFA)