No users are available to approve this request

We are receiving numerous complaints from profile contributors stating that, after submitting a profile creation request, they receive an email saying, “No users are available to approve this request.” This issue commonly arises when a manager has changed roles or left the organization.

  1. Is there a way to automatically update manager information for NERM users?
  2. Additionally, when no manager is available to approve the request, users should either receive a notification, error message, or be prevented from submitting the request altogether. It is frustrating for users to have to resubmit their requests.

Hi Ravindnra,

I am not a NERM expert, but I went through your post & checked the official docs to see what might be going on. Sharing what I found in case it helps you narrow this down.

From what I can see in the docs, NERM doesn’t validate approvers before submission. The Approval Form step resolves the approver at runtime, & if that configuration ends up returning zero active users, the request fails with the error you’re seeing.

Reference: Workflow Actions - SailPoint Non-Employee Risk Management Admin Help

A few things you could try:

1. Keep manager data in sync :
If your approval is based on manager, you could use an automated workflow to pull the latest manager from your authoritative source (via REST API) and update it on the NERM profile regularly.

2. Handle it in the workflow :
Before the Approval Form, add a check to see if a valid manager exists. Based on that, you can branch the logic. If no manager is found, send a notification and close the request cleanly instead of letting it fail.

3. Add a fallback approver :
Instead of relying only on manager, consider adding a role-based approver (NEProfile role / collaboration role). That way the approval step still has someone to route to even if the manager is missing.

One thing I couldn’t find clearly in the docs is how NERM handles inactive or missing approvers internally, or if there’s any built-in fallback. If you need a definitive answer on that behavior, it might be worth raising a support case.

Just sharing what I found & a few things you could try. Curious to see what ends up working in your case