We have Restriction Groups that relate to certain Users seeing certain items. This Restriction Group has worked fine for a couple years. Now it periodically doesn’t work and Users can see items we don’t want them to. We are currently using Acumatica 2025 R1.
Is anyone else experiencing this issue? Is there a fix?
Is the restriction being set by Item Class? Looks like there are a couple of know issues that have workarounds but are still unresolved.
Restriction Groups are generally stable, so intermittent behavior is usually related to caching, configuration changes, or a build-specific issue.
First, confirm the group setup on Restriction Groups (SM201030) and verify that both the users and the specific inventory items are still included in the group. Since this restriction is applied at the item level (not item class), check whether any items were recently imported, copied, or updated through integrations, as those processes can sometimes overwrite or remove restriction memberships.
Second, have affected users log out and back in, or clear the application cache, since visibility can appear inconsistent when session or application cache has not refreshed.
If the configuration is correct and the issue started after moving to Acumatica 2025 R1, it may be related to a build issue. In that case, reviewing the release notes for your specific build or opening a support case would be appropriate.
Eli: Thank you. You have given me several ways to move forward. I currently have the Restriction Group working correctly.
With respect to caching, I wonder if I have been getting false results when I log in as a User via the Users tab, and check to see if the Restricted Items are visible to this User?
Any thoughts on that?
To answer the second part, I can understand why you may be seeing misleading results. When you use “Login as User” from the Users (SM201010) form, the session is created within your existing browser session, so some cached data or permissions from your original login can still persist. Because of that, it is not always a perfect representation of how the restriction behaves for that user in a completely fresh session.
If you want to verify restriction groups more accurately, it is better to test by opening a separate browser or an incognito/private window and logging in directly as that user. That forces a clean session with no shared cache and will give a more reliable view of whether the item-level restriction group is actually preventing visibility.
When I discover that the Restriction Group in no longer working, I have found that I can change the Description line by 1 character, re-save the Restriction Group and it works as needed again.
Again, this worked fine for years. I have changed nothing. None of the Items have changed. Tomorrow morning I can wager it won’t be working again.
Should I start a Case with Acumatica?
Hi
You may find this article helpful:
https://community.acumatica.com/how-tos-and-faqs-231/how-to-configure-restriction-groups-by-user-account-and-subaccount-4263?tid=4263&fid=231
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
