Permissions and approval workflows

Assign Purchase Reports permission

Grant purchase_reports view.

Audience: Purchasing staffPermission: Administrator or relevant status capabilityModule v1.7.9

Exact navigationAdmin Area → Setup → Roles or Purchase → Settings → Permissions

Before you begin

Use an account with Administrator or relevant status capability and confirm the intended record or setting before making a change.
Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.

What this guide covers

Grant purchase_reports view. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Exact step-by-step process

Open Admin Area → Setup → Roles or Purchase → Settings → Permissions.
Select the exact record or option described in this guide.
Complete the displayed fields or action using the rules below.
Save or submit once and resolve any validation response.
Verify the resulting record, status, file, notification or integration effect.

Fields, choices and supported possibilities

Approval setupName, related transaction type, approval type and approver rows/conditions.

DecisionCurrent approver, decision, reason, signature/upload and notification.

FiltersReport type, period/month/year/date range, currency, status and vendor/project filters where displayed.

OutputTable/chart totals derived from purchase records visible to the authorised user.

Code-backed validations and workflow rules

Record access does not automatically grant the dedicated change-status capability.
The module supports configured approval routes for purchase requests, orders, returns and FAF flows.
Reports require purchase_reports view capability.
Figures depend on stored currency/rate, status and date values; reconcile against source records.

Expected result and verification

The supported assign purchase reports permission flow completes without bypassing permission or validation checks.
The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
Unexpected validation, provider or linked-record errors are investigated before retrying.

Security, privacy and operational checks

Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
Test settings and automated jobs with controlled records before production-wide use.