Review backup and checkpoint files as excluded artefacts | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/review-backup-and-checkpoint-files-as-excluded-artefacts Publisher: Pixie Technologies LLC Security, data storage and audit Review backup and checkpoint files as excluded artefacts Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Do not present .bak, .checkpoint, debug logs or error_log files as user features. Audience: CRM staff; Permission: Technical administrator; Module v1.0.0; Where to goDeployment package review Before you start - Use an account with Technical administrator 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 Do not present .bak, .checkpoint, debug logs or error_log files as user features. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow. Follow these steps - Go to Deployment package review. - Select the relevant record, filter, report, model or configuration described below. - Use the displayed action or read the current values without altering unrelated data. - Compare the output with the code-backed rules and expected result in this guide. - Record or correct any mismatch before relying on the output in production. Fields and options Exact actionCheck backup and checkpoint files as excluded artefacts Exact navigationDeployment package review Module version1.0.0 Access ruleTechnical administrator VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect. Rules and limits - Remove unnecessary artefacts from production deployments under an authorised development task; Help Centre excludes them from feature documentation. Check it worked - The supported review backup and checkpoint files as excluded artefacts 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 Understand no registered Real Estate cron hook (https://pixiecrm.com/help-centre/understand-no-registered-real-estate-cron-hook)Run a Real Estate security review (https://pixiecrm.com/help-centre/run-a-real-estate-security-review)Apply least privilege to Real Estate Management (https://pixiecrm.com/help-centre/apply-least-privilege-to-real-estate-management)Review Real Estate email templates (https://pixiecrm.com/help-centre/review-real-estate-email-templates)Troubleshoot Real Estate activation (https://pixiecrm.com/help-centre/troubleshoot-real-estate-activation)Browse all Real Estate Management guides (https://pixiecrm.com/help-centre/category/real-estate-management)Customers Contacts (https://pixiecrm.com/help-centre/category/customers-contacts)Contracts Documents (https://pixiecrm.com/help-centre/category/contracts-documents)Invoices Payments (https://pixiecrm.com/help-centre/category/invoices-payments)