REDList Solutions
Back to ELERA Talk to REDList

Available ELERA application

Manage the people who operate ELERA.

REDList User Management UI gives authorized teams a focused way to find and maintain ELERA users, node-specific roles, home stores, passwords, account state, and history—without exposing ELERA credentials or tokens to the browser.

It also provides the back-office view for REDList fingerprint support in WebPOS and includes a guided path for bringing existing ACE operators into ELERA from EAMOPERA.

View Application Screens
Available Now ELERA 1.2503 Node-aware roles ACE operator import WebPOS fingerprints

Focused administration

A practical user-management surface for ELERA

The application keeps everyday identity and access work understandable while respecting the roles and node scope already defined in ELERA.

Find the right operator

Search a paged ELERA directory by username or name, role, node ID or display name, and fingerprint enrollment state without loading the entire enterprise directory into a browser.

Manage node-specific access

Create and edit users with independent role sets at one or more nodes, select a home store, and limit assignments to the scope and roles held by the signed-in administrator.

Handle account lifecycle

Change or reset passwords, unlock users, enable or disable sign-in, review ELERA history, and use guarded deletion with exact-name confirmation and reauthentication.

Support self service

Users without directory-management access can still update their own name and change their own password through a protected self-service view.

Import ACE operators

Scan a configured or uploaded EAMOPERA keyed file, preview operators, map ACE authorization flags to ELERA access profiles, skip existing users, and monitor the background import.

See fingerprint posture

Show enrolled operators, review non-sensitive enrollment metadata and audit activity, remove an enrollment, and clean up records whose ELERA users no longer exist.

REDList WebPOS fingerprint support

Fingerprint convenience without bypassing ELERA identity.

The operator account and its roles remain in ELERA. WebPOS captures and identifies the enrolled finger, then uses the protected credential workflow associated with that operator. User Management combines the two sources for administration while keeping templates and vault ciphertext off the browser.

Current test hardware: DigitalPersona 4500 Fingerprint Reader with REDList support built on ELERA 1.2503.
Explore Fingerprint Sign-On
1
Authorize in ELERA
Create the user and assign the correct store, home-store, and POS roles.
2
Enroll at WebPOS
The operator registers at the supported reader in the till workflow; the back-office app never captures a finger.
3
Identify and sign in
WebPOS matches the enrollment to the ELERA operator and uses its protected authentication workflow.
4
Maintain centrally
Managers can review status and audit, remove enrollment, or clean up an orphan without deleting the ELERA user.

ACE → ELERA

Turn an ACE operator file into reviewed ELERA accounts

User Management includes a deliberate import workflow for retailers that need to carry operator identity and access intent forward during migration.

1

Choose store and source

Select the ELERA destination and read the configured server-side EAMOPERA file or a file chosen from the current computer.

2

Scan and preview

Validate the keyed-file structure and separate eligible operators, existing ELERA users, unmapped records, model records, and invalid records.

3

Resolve access profiles

Map ACE option flags and levels to cashier, restricted cashier, cash-office, or manager profiles backed by approved ELERA roles.

4

Confirm and monitor

Reauthenticate, confirm the exact node, run the import in the background, and download a result that explains each operator outcome.

Why a standalone app

Fingerprint work made focused user administration useful now.

REDList developed User Management while exploring the next generation of its store tools. While implementing fingerprint reader support on ELERA 1.2503, it became clear that user, access, enrollment, and ACE operator migration work deserved a secure standalone surface that teams could use independently.

Where it is going

Designed to inform Store Director—and remain useful on its own.

User Management capabilities can inform Store Director as the new app takes shape. The standalone application still makes sense for security teams, central administrators, fingerprint support, and deployments that want focused user administration without the broader store-operations workspace.

Preview Store Director

Application screens

See the current User Management workflow

Select any captured screen to inspect the interface at full size.

Planning ELERA user migration or fingerprint-enabled WebPOS?

Talk with REDList about operator conversion, node-role design, User Management UI, DigitalPersona 4500 testing, and a rollout path that connects cleanly with the broader Store Director roadmap.

Talk to REDList View Fingerprint Solution

ELERA USER MANAGEMENT

How the application works

High-level overview

User Management is a secure browser interface for ELERA operator accounts. It lets authorized users find people, review profiles and direct node-role assignments, create or update accounts, manage passwords and account state, and review change history. ELERA remains the source of truth, and the signed-in operator's own roles and node scope determine what can be seen or changed.

Find and review users

Username or name, role, node, and fingerprint filters work together. Results are paged from ELERA instead of downloading a large enterprise directory. Selecting a user exposes direct assignments, account state, identity details, history, and non-sensitive fingerprint information.

Create and manage accounts

Profiles
Create local ELERA users and update identity fields. Usernames remain immutable after creation.
Node assignments
Grant independent role sets at one or more nodes and select exactly one home store.
Account access
Change passwords, unlock accounts, and enable or disable sign-in under ELERA policy.
Removal
Use exact-name confirmation and administrator reauthentication for guarded deletion.

How fingerprints fit in

  1. Create and authorize the ELERA user with the correct store and POS roles.
  2. Enroll the operator at WebPOS using the supported fingerprint reader. User Management never communicates with the USB reader.
  3. WebPOS identifies the enrollment and uses its protected credential workflow for the matching ELERA user.
  4. Managers can review enrollment metadata and audit, remove enrollment, or clean up an orphan. Templates and password-vault ciphertext never enter this website or the User Management browser.

ACE operator import

The import scans a configured or uploaded EAMOPERA keyed file, previews all outcomes, maps ACE flags and levels to stable business profiles, and resolves those profiles to approved ELERA roles. Existing users are skipped. The administrator reauthenticates and confirms the exact destination node before the background job creates users.

Security and failure behavior

  • ELERA authorization tokens remain in server-side sessions and are not stored in browser JavaScript.
  • ELERA permissions remain authoritative; the app also enforces node scope and prevents privilege assignment beyond the administrator's access.
  • Password, delete, and fingerprint-removal workflows use explicit confirmation and reauthentication where required.
  • If the fingerprint database is unavailable, ordinary ELERA user management continues while fingerprint-specific views are temporarily unavailable.