PIM Manager · Features

Changes only what you define - deleting an account is a person's decision

The engine changes groups, roles and admins only when your data defines them, does not disable, revoke or offboard your break-glass accounts, and does not delete a user account on its own.

CommunityPro BusinessPro EnterprisePro MSPChange without fearSecure by design

Guards page listing each guard, its state and the guards that cannot be released
Guards: the locked guards, which cannot be released - a prune does not delete an admin account, memberships in groups PIM Manager does not manage are not removed, and break-glass accounts are not disabled, revoked or offboarded.

Purpose

Adopting an automation tool on a live tenant is only safe if it cannot reach beyond what you hand it.

Design

The engine changes a policy, group, admin or assignment only when your data defines it; if your data defines nothing, the engine changes nothing. Groups, roles and admins that no row names are left alone by the engine; a SuperAdmin can still delete or revoke them by hand, through a commit. Your break-glass accounts are not disabled, revoked or offboarded.

No automatic path deletes an admin account: an auto-disable date disables the account on its date, and the account stays in your directory. Deleting is done by a person with Delete account, confirmed by typing DELETE: a SuperAdmin, or an Admin whose delegated scope and level cover the account. A live admin account you have not defined is reported, not disabled for being missing.

Business opportunities

You can introduce PIM Manager area by area on a production tenant, and existing access outside its scope keeps working as before.

Related features

← Every PIM Manager feature