Requisition Administration — Permissions
Overview
This page documents the permissions used in the Requisition Administration module. Permissions determine which tabs a user can access and which actions are available.
For general access concepts and permission categories, see: Permissions & Access
Permissions by transaction
| Permission | Grants access to |
|---|---|
view |
Access the /requisition-administration screen. View any requisition via the View modal. |
create po |
New PO, Reject, and Finalize row actions (on PEND requisitions). |
Note
viewalone provides read-only access — the user can see all requisitions and open the View modal, but cannot create POs, reject, or finalize.create poimplies the user is a member of the purchasing team with authority to process requisitions.
| Permission | Module | Grants access to |
|---|---|---|
view |
Requisition Administration |
See the Automatic Services and Automatic Contracts tabs. |
edit |
properties |
Edit and Deactivate actions on services and contracts. |
Note
The Automatic Services and Automatic Contracts tabs are owned by the Properties module. A user with Requisition Administration.view but no properties permissions can see the tabs but has no write actions available.
Typical role mapping
-
Purchasing team member
view+create po
-
Read-only (e.g. manager reviewing status)
view
Troubleshooting access
- If the Requisition Administration menu item is missing, the user is missing the
viewpermission for the Requisition Administration module. - If New PO, Reject, and Finalize are missing from the row actions, the user is missing the
create popermission. - If Reject is hidden on a specific regular requisition even with
create po, a PO has already been created from that requisition (valid_pois set). Rejection is intentionally blocked in this case. - If Edit and Deactivate are missing on the Automatic Services or Contracts tabs, the user needs
editpermission for the properties module.
For system-wide troubleshooting, see: Permissions & Access