PIM Manager · Features

One queue for the changes you make - reviewed, backed up, reversible

Configuration edits, revokes, access-pass re-issues and session revokes wait in one queue until someone commits them.

CommunityPro BusinessPro EnterprisePro MSPChange without fearProve compliance

Review and commit queue with pending entries, who requested them and when
Pending changes: configuration edits and queued directory actions, such as a revoke and a Temporary Access Pass re-issue, in one queue, ready to commit.

Purpose

A wrong click in a privileged-access tool is expensive. Changes made straight to the tenant cannot be reviewed beforehand or cleanly undone afterwards.

Design

A change you make in the Manager is staged in Pending changes, where a keyed diff shows exactly what is added, changed or removed; reordering rows is shown as no change. PIM Manager does not commit a change you staged on your behalf. Staged edits are kept in PIM Manager's database, so they survive a page reload, and administrators see each staged change and who staged it. A commit first re-checks the changes and lists any blocking error with the rows it concerns and a link to its fix.

Before a commit is written, the affected data is backed up. The commit writes your model in one database transaction: if any part fails, the whole change to the model is rolled back, and the engine then applies the committed model to the tenant item by item. Backups / Undo lists the recent snapshots and plans the inverse change, which you commit through the same checks. A few changes follow a rule you set instead of a commit, such as a passing auto-disable date; each runs inside the guards and is written to the audit trail.

Business opportunities

Administrators can work quickly because mistakes are caught before they land and can be reversed after. Change advisory boards get a clear, reviewable list instead of a description.

Related features

← Every PIM Manager feature