Require a department on purchase requests | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/require-a-department-on-purchase-requests Publisher: Pixie Technologies LLC Settings, numbering, PDFs and vendor-portal options Require a department on purchase requests Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Enable pur_department_required_condition. Audience: Purchasing staff; Permission: purchase_settings: Edit; Module v1.7.9; Where to goAdmin Area → Purchase → Settings → Purchase Options Before you start - Use an account with purchase_settings: Edit 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 Enable pur_department_required_condition. 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 → Purchase Options. - 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 Request headerRequest code/name, requester, type, department, project, related sales estimate/invoice, currency and rate. Request linesItems, description, quantity, unit, tax, price, discount, subtotal and total. SourcingSelected vendors, attachments, public share/request-for-quotation actions and approval status. Rules and limits - Save through the module settings form and test with a controlled transaction. - Do not change unrelated purchase options during a scoped configuration update. - Purchase-request status changes use the dedicated purchase_request status capability in addition to record access. - Department can be mandatory when pur_department_required_condition is enabled. Check it worked - The supported require a department on purchase requests 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 Show terms and conditions on purchase-order PDFs (https://pixiecrm.com/help-centre/show-terms-and-conditions-on-purchase-order-pdfs)Require a project on purchase orders (https://pixiecrm.com/help-centre/require-a-project-on-purchase-orders)Configure purchase-order numbering (https://pixiecrm.com/help-centre/configure-purchase-order-numbering)Purchase Management module overview (https://pixiecrm.com/help-centre/purchase-management-module-overview)Understand Purchase Management capability groups (https://pixiecrm.com/help-centre/understand-purchase-management-capability-groups)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)