IdStory Identity Manager

New Workflow Engine - [Workflow Agenda]

koulaj (koulaj@undisclosed.example.com) — 2026-04-29T22:41:14+00:00

New Workflow Engine IdStory IDM version 15+ includes a proprietary workflow implementation for use in approval processes. The goal is to enable administrators to configure approval processes easily and flexibly, with full control over the sequence and conditions of approval steps. Auditability and robustness of the entire process are ensured.

Automatic role definitions - Import all rules

hoday (hoday@undisclosed.example.com) — 2026-04-29T14:49:58+00:00

Automatic role definitions - Import all rules This LRT - ImportAutomaticRoleByAttributesCSVExecutor will let you import automatic roles definitions by attribute. You are able to import dynamic number of rules to each role definition. Supported attributes types are:

screenshot2026-04-29at16.32.01.png - created

hoday (hoday@undisclosed.example.com) — 2026-04-29T14:32:55+00:00

20260429-142437.png - created

otmara (otmara@undisclosed.example.com) — 2026-04-29T14:24:37+00:00

Synchronization of roles/groups - [Assign roles to all valid contracts]

otmara (otmara@undisclosed.example.com) — 2026-04-29T14:24:37+00:00

Synchronization of roles/groups sync role groups Role synchronization works according to the same rules as identity synchronization. In this page we will described only extra behavior specific for this synchronization. What is a role and a group? A role in IdM is a basic entity that is used to define permissions in IdM. Therefore, if such a role is assigned to an identity, the identities obtain the permissions that are defined on the role. In addition to permissions in IdM, a role can define…

Identities (users) - [User guide]

hoday (hoday@undisclosed.example.com) — 2026-04-29T12:51:54+00:00

<- .:start | Documentation ^ .:start | Documentation ^ .:contracts | Contracts → Identities (users) In identity management, identity is a set of information that describes a real person. Some of the information like First Name, Last Name, Login or Password is crucial for many IT systems, since they process them, or e.g. use them for authentication or authorization. Identity management systems process the data about identity, transform them and use them to manage accounts on connected systems.…

User filter agenda: - created

hoday (hoday@undisclosed.example.com) — 2026-04-29T12:42:15+00:00

User filter agenda: This agenda allows admin to filter users according to assigned and unwanted role:

userfilters.png - created

hoday (hoday@undisclosed.example.com) — 2026-04-29T12:41:31+00:00

Connector configuration and attribute mapping

cem (cem@undisclosed.example.com) — 2026-04-29T11:59:52+00:00

Connector configuration and attribute mapping connector mapping system configuration merge authoritative skip excluded Connector configuration connector configuration Creation of a newly connected system will be demonstrated on a database connector (ConnIdDBBundle). Firstly, we will create a new system named Table and choose the database connector. All settings for this connector are available in the

20260429-075115.png - created

koulaj (koulaj@undisclosed.example.com) — 2026-04-29T07:51:15+00:00

Technical Account Module - Technical Assets - [Bulk Actions]

kolombom (kolombom@undisclosed.example.com) — 2026-04-28T08:39:07+00:00

Technical Account Module - Technical Assets Overview The 'Technical Asset' extends CzechIdM's technical account module capabilities by introducing a new entity type that groups and manages technical accounts. This module enables organizations to associate technical accounts with specific assets, assign guarantors and holders through both direct assignment and role-based mechanisms, and implement comprehensive audit trails for all operations.

ImportTechnicalAccountsFromCSVExecutor

cem (cem@undisclosed.example.com) — 2026-04-28T08:01:50+00:00

ImportTechnicalAccountsFromCSVExecutor Long Running Task (LRT) that bulk-creates or updates Technical Accounts in CzechIdM by reading a semicolon-separated CSV file. Each CSV row represents one technical account. The task maps configurable column names to entity fields, supports dry-run mode, and never triggers unintended provisioning operations on existing accounts.

technical_asset_accounts_1.png - created

koulaj (koulaj@undisclosed.example.com) — 2026-04-27T23:49:07+00:00

technical_asset_audit.png - created

koulaj (koulaj@undisclosed.example.com) — 2026-04-27T23:10:50+00:00

technical_asset_holders.png - created

koulaj (koulaj@undisclosed.example.com) — 2026-04-27T23:10:11+00:00

technical_asset_accounts.png - created

koulaj (koulaj@undisclosed.example.com) — 2026-04-27T23:08:25+00:00

technical_asset_guarantors_1.png - created

koulaj (koulaj@undisclosed.example.com) — 2026-04-27T23:07:52+00:00

technical_asset_guarantors.png - created

koulaj (koulaj@undisclosed.example.com) — 2026-04-27T23:06:04+00:00

technical_asset_info.png - created

koulaj (koulaj@undisclosed.example.com) — 2026-04-27T23:02:52+00:00

technical_assets.png - created

koulaj (koulaj@undisclosed.example.com) — 2026-04-27T23:01:41+00:00