Understand record-retention limitation | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/service-journeys-data-audit-security-no-hard-delete Publisher: Pixie Technologies LLC Stored data, audit continuity and security Understand record-retention limitation Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. No user-facing delete/hard-delete workflow is supplied. Audience: Service delivery staff, compliance managers, administrators, linked client contacts and public applicants; Permission: View or Administrator; Module v1.0.0; Where to goAdmin Area → Projects & Work → Service Journeys Before you start - Verify the module is active and use the exact navigation shown above. - Use an account with the stated module and core CRM permissions. - Use known test records when changing statuses, visibility, saved filters or global navigation. What this guide helps you do No user-facing delete/hard-delete workflow is supplied. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow. Follow these steps - Go to Admin Area → Projects & Work → Service Journeys. - Find the record, endpoint, field or action used to understand record-retention limitation. - Complete the displayed values exactly as described in this guide. - Select the available save, submit, send, upload, create, update or confirm action. - Return to the related register, portal, activity log or API response and verify the expected result. Fields and options Workspace or endpointAdmin Area → Projects & Work → Service Journeys PurposeNo user-facing delete/hard-delete workflow is supplied. Rules and limits - The action is available only where the supplied module exposes it and the signed-in user or API client meets the stated access conditions. - Internal helpers are documented under the visible workflow or endpoint they support rather than presented as invented menu pages. Check it worked - The understand record-retention limitation workflow completes without a validation, permission, ownership or availability error. - The related record, portal view, activity entry, notification log or API response shows the expected state. - Client-visible, public and API data remains limited to the code-backed ownership and visibility rules. Security, privacy and operational checks - Use controlled test records and non-production credentials before wider rollout. - Grant least privilege and protect secure links, personal data, uploaded files, signatures, API tokens, allowed origins and server IPs. Related guides Preserve audit continuity on deactivation (https://pixiecrm.com/help-centre/service-journeys-data-audit-security-deactivation)Understand public page indexing (https://pixiecrm.com/help-centre/service-journeys-data-audit-security-public-noindex)Stored data, audit continuity and security (https://pixiecrm.com/help-centre/topic/service-journeys-data-audit-security)Browse all Service Journeys guides (https://pixiecrm.com/help-centre/category/service-journeys)Projects, tasks and time tracking (https://pixiecrm.com/help-centre/category/projects-tasks)Client portal overview (https://pixiecrm.com/help-centre/client-portal-overview)Create a task (https://pixiecrm.com/help-centre/create-a-task)Upload and share customer files (https://pixiecrm.com/help-centre/upload-and-share-customer-files)Configure SMTP email delivery (https://pixiecrm.com/help-centre/configure-smtp-email-delivery)Review email delivery issues (https://pixiecrm.com/help-centre/review-queued-email-and-delivery-issues)