Acos Websak
This document describes the integration between eADM and Acos Websak. The integration automates user account management in Acos Websak by synchronizing user and role information from eADM.
Overview
When an employee is granted access to Acos Websak, a user account is automatically created. This account is continuously updated and will be deactivated when the employee's tenure ends. Roles within Acos Websak can also be managed automatically through rule sets defined in eADM or assigned by a department manager. Additionally, the integration can maintain the organizational hierarchy in Acos Websak using data imported into eADM from the organization's HR system.
Note: When users or departments are removed from the HR system, their corresponding entries in Acos Websak are deactivated, not permanently deleted. An account cannot be deleted from Acos until all cases and records have been removed from the user.
Pre-configuration
Before Identum can set up the integration, you must perform the following preparatory steps in collaboration with Acos.
1. Order the Integration from Acos
You must first contact the Acos marketing department to order the integration and have them create the necessary "template users." These template users are used to assign system access for different roles, such as Archivist, Committee Secretary, Manager, or Case Officer.
When ordering, ask Acos to provide the GID (unique IDs) for the template users they create. These IDs are essential for the integration.
To order the integration contact the following personnel at Acos:
Lene Hellesøy: lene@acos.no, Tel: 93 21 87 28
Eivind Svellingen: es@acos.no, Tel: 92 26 22 20
For status on existing order contact:
Asle Brakstad: asle@acos.no, Tel: 46 42 05 07
2. Obtain API Credentials from Acos
Acos will provide you with the following API credentials required for the integration.
Information | Value | Description |
|---|---|---|
API URL | [Customer Specific] | The URL for your organization's API endpoint. Ex: |
Client ID | [Provided by Acos] | The ID for the API user. This is often the same value as the Scope. |
Client Secret | [Provided by Acos] | The password for the API user. |
Scope |
| The identifier for the API to be used. This is typically |
Top Node ID | [Provided by Acos] | The ID of the highest-level node in your Acos organizational hierarchy |
Note: In some configurations, the Client ID and Client Secret may have the same value.
3. Prepare Existing Data in Acos Websak
To ensure a successful synchronization, you must align existing user and department data in Acos Websak with the data in eADM.
Link Existing Users
To connect users from the HR system with their existing accounts in Acos Websak, they must share a matching username or email address. Ensure that the email address and/or username in Acos Websak matches the user's primary work email in eADM.
Warning: If this alignment is not performed correctly, the integration will create duplicate user accounts.
Link Existing Departments
To connect departments from the HR system with their corresponding departments in Acos Websak, they must share a unique ID. This is typically the department number found in eADM. You must enter this number into the departmentid field for the corresponding department in Acos.
Warning: If this alignment is not performed correctly, the integration will create duplicate departments.
Configuration
Once the pre-configuration steps are complete, Identum will finalize the setup.
1. Define Role Assignment Rules
You need to define the rules that determine which employees are automatically assigned a specific role or template user in Acos. Based on your requirements, Identum will create the necessary access control rules.
Example of Role Assignment Rules:
Template User | Assignment Rule |
Archivist | All employees in department 5760 (Archive). |
Committee Secretary | [Defined by customer] |
Manager | All users with the "Manager" role. |
Case Handler | All employees in the Building Affairs, school administration, and Finance departments. |
Note: These rules do not need to be finalized beforehand. We can define them together in a workshop.
2. Notify Identum
When all the preparatory steps are completed, please notify Identum. We will then proceed with the final configuration and activation of the integration.
Advanced Configuration (Optional) - Linking Multiple eAdm Departments to a Single Acos Department
This type of configuration should generally be avoided, and a 1:1 department mapping is recommended.
If necessary, multiple departments in eAdm can be mapped to a single department in Acos. To do this, enter the eAdm department numbers into the departmentid field in Acos, separated by a pipe character (|).
Example: 6705|5794|6347 With this configuration, all user data from departments 6705, 5794, and 6347 in eAdm will be synchronized to the same department in Acos.