Safe Bulk policy

Three possible outcomes

Before a bulk decision, Approval Desk evaluates each selected request against the native approval state and any administrator-configured Safe Bulk rules.

Eligible

The approval is still pending, belongs to the configured scope, can be answered by the signed-in user and passes the configured policy. It can be included in the confirmed batch.

Individual review required

The request is not suitable for this batch — for example, a request-type rule blocks bulk processing, the request is outside the configured scope or the signed-in user cannot answer it. The app states Individual review required and gives the available reason.

This does not mean the request cannot be approved. Open it and follow the normal individual review path where the native JSM permission allows it.

Evaluation could not be completed

If a policy check cannot be evaluated because of a technical or API problem, Safe Bulk fails closed. The request is kept out of the batch and requires individual review until the state can be verified.

Why fail closed matters

Approval is a business-significant action. A missing check must never be interpreted as permission to include an item. The app also re-checks the native approval state immediately before execution to reduce stale decisions.