Customer work, connected.

Help & supportMyAccount
Six-stage managed-service workflow

Stage 4: Portfolio Review

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Complete the portfolio/service review.

Audience: Service delivery staff, compliance managers, administrators, linked client contacts and public applicantsPermission: EditModule v1.0.0
Jump to steps
Where to goAdmin Area → Projects & Work → Service Journeys → Application → Workflow → Complete stage
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

Complete the portfolio/service review. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

  1. Go to Admin Area → Projects & Work → Service Journeys → Application → Workflow → Complete stage.
  2. Find the record, endpoint, field or action used to stage 4: portfolio review.
  3. Complete the displayed values exactly as described in this guide.
  4. Select the available save, submit, send, upload, create, update or confirm action.
  5. Return to the related register, portal, activity log or API response and verify the expected result.

Fields and options

StageStage 4: Portfolio Review
Compliance managerRequired for stage 2; hidden/zero for other stages unless the view provides it.
NoteOptional stage evidence.

Rules and limits

  • Complete earlier stages first.
  • Stage completion is retained as workflow history.

Check it worked

  • The stage 4: portfolio review 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.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page