Assign Purchase Settings permission
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Grant purchase_settings edit only to authorised configuration administrators.
Where to goAdmin Area → Setup → Roles or Purchase → Settings → Permissions
Before you start
- 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 helps you do
Grant purchase_settings edit only to authorised configuration administrators. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to 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.
- Check the resulting record, status, file, notification or integration effect.
Fields and options
Approval setupName, related transaction type, approval type and approver rows/conditions.
DecisionCurrent approver, decision, reason, signature/upload and notification.
Rules and limits
- 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.
Check it worked
- The supported assign purchase settings 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.
Related guides
Was this guide useful?Your response is stored only in this browser.