Skip to main content
Disable one or more accounts or identities directly from Human Identities, without leaving Oleria. Choose whether the action needs an approver’s sign-off first, or should run immediately - it’s your call each time.
Only Administrators can disable accounts, where your workspace has this action enabled. Operators can build the scheduled Disable dormant accounts workflow instead. View role permissions.
1

Select what to disable

Select the accounts or identities to disable from one of these places:
  • Human Identities -> Hygiene - useful for dormant accounts, since you can filter by dormant days first.
  • Human Identities -> Inventory, on the Identities tab or the Application accounts tab.
Filter the list if you need to, then select one or more rows.Some rows can’t be selected - for example, accounts that are already disabled, machine accounts (not currently supported for this action), or accounts on an application that doesn’t have remediation write permissions enabled.
2

Start the disable action

Select Disable identities (on the Identities tab) or Disable accounts (on the Application accounts tab or Hygiene). This opens the Disable accounts or Disable identities dialog, depending on where you started.
3

Decide whether this needs approval

Turn on Configure approval to disable accounts to route the action to an approver first - nothing changes until they approve it. It’s off by default, so leaving it as is disables the selected accounts or identities right away.If you turn it on, choose who approves it: Manager (the manager of the employee linked to each selected account) or Specific user. If you choose Manager, also set an alternate approver, who gets the request when an account has no manager on record or the manager has no work email. You can also select Notify Me to be emailed when the approval and the disable action complete.
This is different from the Disable dormant accounts scheduled workflow, where approval is on by default. This one-off action is off by default instead - either can be changed by whoever configures it.
You can also add an optional reason, up to 150 characters. It’s included in the audit trail, and shown to the approver if approval is required.
4

Submit

Confirm to submit the action.
If you select an account that already has an active disable action in progress, Oleria shows a warning - but you can still continue, which starts a second, overlapping action for that account.

Track the action

Every disable action runs as a workflow. After you submit, a toast message appears with a View details link that opens the workflow in the workflow builder. To see the status of each account or identity it affected, go to Action Center instead, where the action also appears alongside your other remediation actions - you can check its status and undo it within 7 days if needed.
The account’s status in Oleria also depends on the next data sync with the integrated application; to verify immediately, check the target application directly.

Automate this with a scheduled workflow

For a scheduled version of this action, with approval on by default, see Disable dormant accounts.

Contact us

For questions, contact us at support@oleria.com.