Summary (TL;DR): Resolve "Access Restricted" errors or a missing Procure tab by adjusting role permissions and verifying Location or Department access levels.
The Issue
Users may be unable to see the Procure tab, view Purchase Orders (POs), or may encounter an "Access Restricted" error when attempting to comment on a PO even if other modules like Order Requests are visible.
Additionally, users may encounter a scenario where they can create POs for orders submitted by others but not for their own approved orders.
Potential Causes
Missing role permissions: The user's assigned role does not include the Procure or Create and View Purchase
Orderspermission.Permission misconfiguration: The user's Request and Procure department permissions are misaligned, blocking access to their own approved orders.
Location or department mismatch: The user lacks access to the specific Location or Department associated with the PO's Billing Address.
Billing Address logic: Unlike requests, PO access is governed by the Billing Address location, not the item's delivery location.
Resolution Steps
1. Enable Procure Role Permissions
A Superuser must grant the foundational permission to access the module.
Navigate to Settings > Manage Users.
Select the applicable user and click the Roles & Permissions tab.
Click Edit Permissions.
Check the box for Procure, or use the dropdown arrow to select specific granular permissions like Create and View Purchase Orders.
Click Apply.
2. Assign Location & Department Access
If the user has the correct role but still cannot see specific POs, verify their organizational access.
In the user's Roles & Permissions tab, locate the Procure permission line.
Click the Locations button next to Procure.
Select the Locations that match the PO Billing Addresses and click Assign selected locations.
If applicable: If your domain uses "Procure by Department," click the Departments button and ensure the correct departments are selected.
In the Procure module, verify the location and department associated with the request that the user is unable to process, in order to identify any missing permissions.
NOTE: Standard Create and View Purchase Orders permissions do not always require specific location assignments, but full Procure roles do require them to filter data visibility correctly. Make sure the user's Request and Procure permissions are consistent; mismatches can prevent users from processing their own approved orders.
Escalation Path
If the Procure tab is still missing after completing the steps above, contact your internal Procurify Administrator to check for conflicting custom roles or domain-level restrictions.