Owl IDM documentation¶
Owl IDM is a lightweight identity management system. It keeps people's access in step with their working life: accounts and groups are created when someone joins, adjusted when they move, suspended while they are away and removed when they leave — and every account stays accounted for.
This site explains how that works out of the box, and how to operate and adjust it.
-
What Owl IDM does on its own when a person joins, moves, goes away for a while or leaves — and which setting decides each step.
-
How to configure the pieces: account definitions, business roles, what departments and positions grant, account names, the nightly jobs, and how to watch provisioning.
-
A one-page map of where each decision is made.
Where the screens are¶
The pages refer to screens by their place in the side menu, for example Access › Account definitions. The menu groups every screen by what it is for:
| Group | What you find there |
|---|---|
| My work | Dashboard, requesting access, approvals, your access reviews |
| Identities | Identities, the organisation (departments, locations, employments), user groups, delegations |
| Access | Business roles, account definitions, privileges, the shop catalogue, orders |
| Governance | Account review, access reviews, segregation of duties, audit history, reports |
| Connectivity | Provisioning, target systems, synchronisation, plans, gateway agents |
| Automation | Processes, scheduled tasks, notifications, computed field rules |
| System | Settings, application log |
You only see the screens your role allows.
About the examples¶
Where a page shows concrete values — business roles, groups, organisational units — they are
examples from a demo environment: a fictional company, demoinc, with an HR system and an Active
Directory domain demoads.local. Your own installation will have its own names; the mechanisms are
the same.