Use the enforced verified-stamp size limits | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/use-the-enforced-verified-stamp-size-limits Publisher: Pixie Technologies LLC Version 2.1.1 update and safety hardening Use the enforced verified-stamp size limits Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Follow this guide to configure verified-stamp width from 78–118 and height from 29–44. Audience: CRM administrator; Permission: Administrator; Module v2.1.1; Where to goAdmin Area → Setup → Settings → General → QR Code Manager Before you start - Use an account with 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 Configure verified-stamp width from 78–118 and height from 29–44. 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 → Settings → General → QR Code Manager. - 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 actionUse the enforced verified-stamp size limits Exact navigationAdmin Area → Setup → Settings → General → QR Code Manager Module version2.1.1 VerificationVerify the described lifecycle, setting, PDF or compliance evidence behaviour in the same workspace. Rules and limits - Stamp width is clamped to 78–118. - Stamp height is clamped to 29–44. Check it worked - The supported use the enforced verified-stamp size limits 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 Use the enforced QR size limits (https://pixiecrm.com/help-centre/use-the-enforced-qr-size-limits)Understand safer Invoice, Payment and Credit Note data access (https://pixiecrm.com/help-centre/understand-safer-invoice-payment-and-credit-note-data-access)Upgrade QR Code Manager to version 2.1.1 (https://pixiecrm.com/help-centre/upgrade-qr-code-manager-to-version-2-1-1)Browse all QR Code Compliance guides (https://pixiecrm.com/help-centre/category/qr-code-compliance)Invoices Payments (https://pixiecrm.com/help-centre/category/invoices-payments)Data Privacy Security (https://pixiecrm.com/help-centre/category/data-privacy-security)Client Portal (https://pixiecrm.com/help-centre/category/client-portal)