Delete a staff-specific Purchase permission assignment | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/delete-a-staff-specific-purchase-permission-assignment Publisher: Pixie Technologies LLC Permissions and approval workflows Delete a staff-specific Purchase permission assignment Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Remove a module-specific assignment without changing unrelated role permissions. Audience: Purchasing staff; Permission: Administrator or relevant status capability; Module v1.7.9; Where to goAdmin Area → 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 Remove a module-specific assignment without changing unrelated role permissions. 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 → Purchase → Settings → Permissions. - Go to the exact record and review linked documents, payments, approvals, files and portal visibility. - Select the supported Delete, Remove, Void or Cancel action. - Verify the action only after checking the consequence described below. - Return to the list and verify whether the record was removed, retained with a status, or blocked by a code-backed restriction. 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 delete a staff-specific purchase permission assignment 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 Review staff-specific Purchase permissions (https://pixiecrm.com/help-centre/review-staff-specific-purchase-permissions)Understand Purchase Management capability groups (https://pixiecrm.com/help-centre/understand-purchase-management-capability-groups)Configure purchase-order numbering (https://pixiecrm.com/help-centre/configure-purchase-order-numbering)Create a vendor (https://pixiecrm.com/help-centre/create-a-vendor)Browse all Purchase Management guides (https://pixiecrm.com/help-centre/category/purchase-management)Expenses Finance (https://pixiecrm.com/help-centre/category/expenses-finance)Invoices Payments (https://pixiecrm.com/help-centre/category/invoices-payments)Contracts Documents (https://pixiecrm.com/help-centre/category/contracts-documents)