This article outlines the features available in eAdm simplify your role as an application or system manager. eAdm and should automate routine tasks, freeing you up to focus on other priorities. We have divided these features into four levels, with an increasing degree of automation.
Level 1: Automated Notifications and Orders
eAdm automatically send you a notification or an access order whenever an employee is granted a permission in eAdm. This applies whether the access is assigned automatically based on rules or manually by a manager. For example, when a new employee is granted access to the patient record system Cosdoc, an email alert can be sent to the application manager. Similarly, eAdm notify you when a user is scheduled to lose access.
This feature works for all systems, including those not on our official integration list. Simply let us know what the notification should include, when it should be sent, and who should receive it, and we can set it up for you.
Level 2: Automated Enrollment in Access Groups
eAdm manage user enrollment in access groups across on-premises Active Directory (AD), Azure AD, and Google Workspace. This is useful if your organization uses access groups to control application access—for example, by making a Citrix login icon appear on a user's desktop only when they are a member of the correct group.
This can be combined with other notifications, such as an email to a manager listing the access privileges a new employee has been automatically granted. eAdm also enforce rules to revoke access based on inactivity, for example, by revoking Citrix access if a user has not logged in for 30 days.
Level 3: Automated User Provisioning
In many cases, eAdm create, maintain, and deactivate accounts directly within your application. This depends on the application's ability to receive user data, either through a one-way file transfer (such as CSV or XML) or a two-way API connection.
For example, when user data is received from HR, eAdm synchronize it with an application like Compilo, ensuring that the user account remains up to date. If an employee resigns, the user account in the application is automatically deactivated. We can also apply filters to control which users are exported, such as "only permanent employees" or "all staff in the Health department, excluding kitchen staff."
Level 4: Automated Access Management
When an API-based integration is possible, eAdm often manage not only user accounts but also the specific permissions those users have within the application.
For example, in the case management system Public360, eAdm use rules to automatically assign "Manager" or "Case Handler" roles. These rules can be very precise, granting access only when multiple criteria are met, such as combining job title ("Consultant"), department ("Medical Office"), and employment type ("Permanent"). This ensures that access is tightly and automatically controlled based on an employee's current role and placement.
FAQ: Can My Application Be Managed by eAdm?
The extent to which automation is possible depends on the application. Generally, modern cloud-based systems offer more integration options than older, on-premises applications.
We maintain a list of all the applications our customers use and their integration capabilities: Supported System Integrations.
Here is how the automation levels correspond to the integration types on that list:
-
Level 1 (Notifications): Applies to all systems, even those not on the list.
-
Level 2 (Group Enrollment): Available for systems marked with AD, Azure AD, or Google.
-
Level 3 (User Provisioning): Available for systems marked with API, CSV, or XML.
-
Level 4 (Access Management): Available for systems marked with API.
What if my application isn't on the list?
We can still help! We are actively developing 1–2 new integrations per month and are always looking to expand our library.
Please contact salg@identum.no, and we will look into the options for your system.