Review client journeys | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/service-journeys-messages-client-portal-list Publisher: Pixie Technologies LLC Secure messages and client portal Review client journeys Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Clients see their owned journey list. Audience: Service delivery staff, compliance managers, administrators, linked client contacts and public applicants; Permission: Authenticated client contact; Module v1.0.0; Where to goClients Area → 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 Clients see their owned journey list. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow. Follow these steps - Go to Clients Area → Service Journeys. - Find the record, endpoint, field or action used to review client journeys. - 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 endpointClients Area → Service Journeys PurposeClients see their owned journey list. 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 review client journeys 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 Understand client journey ownership (https://pixiecrm.com/help-centre/service-journeys-messages-client-portal-ownership)Open a client journey (https://pixiecrm.com/help-centre/service-journeys-messages-client-portal-view)Secure messages and client portal (https://pixiecrm.com/help-centre/topic/service-journeys-messages-client-portal)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)