eADM
eADM
Breadcrumbs

Sikri Elements

This document outlines the necessary preparations and required information for integrating eADM the Sikri Elements case and archive system.


Overview

Sikri Elements is a leading case and archive system in the Norwegian public sector, developed from the ESA and ePhorte products.

This integration enables eADM manage the entire lifecycle of users and departments within Sikri Elements, based on source data from your organization's HR and payroll system.

  • Automated Provisioning: Users are automatically created, managed, and deactivated. They are assigned to the appropriate departments and are automatically removed when they change roles or leave the organization.

  • Role Management: eADM user access in Elements through role-based controls. This can be fully automated based on rules or managed manually through the eADM interface.

  • Real-Time Synchronization: The integration is API-based and can run in real time to ensure that data is always up to date.


Pre-configuration

Before the integration can be configured, several preparatory steps must be completed. These are divided into actions you must perform in your own environment and information you need to gather from Sikri.

Customer-Side Configuration

You must configure the following on your systems:

  1. Define Role Scope: Decide which specific roles in Elements eADM be responsible for managing.


Warning: The roles managed by eADM be updated automatically. Role assignments made in eADM become the definitive source for those roles. Any manual assignments of these specific roles made directly in Elements will be removed during synchronization. It is critical to ensure that the rules and assignments in eADM correct and comprehensive.


  1. Define Automation Rules: Determine which users or departments should be assigned roles automatically or have them available for manual assignment. This is necessary to create the corresponding rule sets in eADM. Be sure to include all roles currently in use, regardless of whether they are assigned automatically or manually (see the warning above).

  2. Define Access Levels: Determine which access level codes should be set by default for each role.

  3. Match Department IDs: Match the departments in Elements with those in eADM. The

    Unit abbreviation for this level The field for a department in Elements must be filled in with the corresponding Department Number from eADM.

  4. Match Existing Users: Ensure that all existing user profiles in Elements contain the correct employee number or username. This is required so that eADM match and link the profiles to the correct users from the HR system.

  5. Configure Notifications (Optional): If you want eADM send automatic email notifications (e.g., to an archivist) when access is granted or revoked, you must notify Identum.


Information Required from Sikri

You must obtain the following technical details from Sikri and provide them to Identum:

  • Database Name ( we strongly recommend ordering a test database from Sikri)

  • API User Credentials (Username and Password)

  • Config ID (for both production and test environments, if possible)

  • Record-Keeping Unit Code: The code for the official record-keeping unit (e.g., "SP" for a central mail reception).

  • API URI: This is required if you have a local (on-premises) installation of Sikri Elements.


Kickoff Meeting

Once the prerequisites are in place and Identum has received the necessary access details, we will schedule a kickoff meeting. During this meeting, we will review and approve the final setup and schedule the go-live for either the test or production environment.