This article explains the correct procedure for changing user information in eADM, such as a name, phone number, email address, or username.
In eADM, user data is managed from a central, authoritative source system to ensure data quality and consistency. This means user profile information cannot be changed directly in the eADM interface — with one exception: eADM administrators can manually override data received from the source system.
How data is managed
eADM follows the principle of a Single Source of Truth (SSOT). The source system for eADM is your organisation's Human Resources Management (HRM) system. eADM synchronises user data from the HRM system automatically, ensuring that information is consistent across all integrated platforms.
Note: eADM administrators can manually override user attributes received from the HR system. An override is permanent and will not be overwritten by subsequent synchronisations until an administrator revokes it.
Changing personal information
Personal details must be updated in the HRM system. Once the change is saved there, it will synchronise automatically to eADM.
Contact your HR department to change the following:
-
Full name
-
Address
-
Personal phone number
-
Private email address
-
Manager or department
Changing account and identity information
The following data points are critical identity identifiers that affect login and access across multiple systems. Changes to these must be handled by your IT department.
-
Username (
samAccountName) -
User Principal Name (UPN)
-
Primary work email address
Warning: Changing these identifiers without following the correct procedure can result in loss of access to digital services, files, and third-party applications. Always contact your IT department.
How eADM manages samAccountName
Active Directory (AD) is the master data source for samAccountName in a standard eADM setup. The following rules apply:
-
When eADM creates a new user account in AD, it sets
samAccountNameaccording to the username standard configured in eADM. -
After initial account creation, eADM does not automatically change
samAccountNamefor existing accounts. This is the default behaviour and is intentional — automatic renaming of existing AD accounts is rarely desirable. -
If
samAccountNameis changed directly in AD, eADM will reflect the updated value on the next full synchronisation. Any other connected target systems that usesamAccountNamewill likewise be updated at that point.
Note: eADM can be configured to act as the master data source for samAccountName, so that changes in eADM propagate to AD. This is a non-default configuration and is not recommended in most deployments, as it allows eADM to overwrite existing AD usernames automatically.
Summary
|
Type of data |
Examples |
Where to change it |
Who to contact |
|---|---|---|---|
|
Personal information |
Name, phone number, address |
HRM system |
HR department |
|
Account identity |
Username, UPN, work email |
Active Directory / Entra ID |
IT department |
Administrator override in eADM
This procedure is exclusive to eADM and can only be performed by authorised administrators.
An eADM administrator can override any user attribute received from the HRM system, including samAccountName. The override is permanent and will not be overwritten by subsequent synchronisations. It remains in effect until an administrator manually revokes it.
Warning: Overriding source system data creates a deliberate difference between eADM and the HRM system. Use only when necessary, and ensure your organisation has a clear policy for when overrides are permitted and how they are tracked.
Related articles
-
[TODO: add public docs.identum.no link to: Slik overstyrer du brukerdata i eADM]
This article describes how user data is managed in eADM and the correct procedure for requesting changes to personal information, account identifiers, or source system overrides. It covers the Single Source of Truth principle, the role of the HRM system, the default behaviour of samAccountName as an AD-mastered attribute, and the administrator override capability. The intended audience is system administrators and end users at Identum's municipal customers.