Neighborhood – Deactivate users

[Christopher W]

Neighborhood members can be added manually or automatically (via User Assignment Rule, executed daily via Scheduled Job).
To add members manually, create a record in the Workplace Profile Location Assignments Related List either on the Neighborhood Record or the User Workplace Profile Record. The automatic approach to adding members also creates these records.

However, if it is necessary to remove a user who was previously added automatically, it is not sufficient to set the Active field of the Workplace Profile Location Assignments Record to false. When the User Assignment Rule is executed daily, new active records are created. The reason for this is that only active records are taken into account in the script include “WPNeighborhoodUserUtilsSNC” using addActiveQuery().

Does anyone know the technical reason for this?

[Matthew_13 · Accepted solution]

Hi My Friend,

This is happening because of how the Neighborhood assignment job is built — it’s not looking at who used to be assigned, its only looking at who is actively assigned right now.

When the daily User Assignment Rule runs, it checks:

• does this user meet the rule?

• do they already have an active assignment?

Since the script include (WPNeighborhoodUserUtilsSNC) only queries active records, the moment you set one to inactive the system treats it like the user was never assigned.

So on the next run, it simply adds them back again.

Basically:
Inactive ≠ excluded
Inactive = not assigned anymore → rule adds them again

There isnt a built-in “do not auto-assign this user” state, which is why this loop happens.

If you truly need someone removed and kept out, the fix isnt deactivating the record — its adjusting the assignment rule so that user no longer qualifiesor adding an exclusion condition/flag the rule respects.

@Christopher W - If help answer, Please mark Solution Accepted and Thumbs Up.