Customer work, connected.

Help & supportMyAccount
Review, e-signature and final submission

Type the e-signature full name

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

The typed full name is required for final signature evidence.

Audience: CRM administrators, project teams, developers, authorised client contacts and public prospectsPermission: Secure-link recipientModule v1.1.1
Jump to steps
Where to goSecure recipient link → Review & Submit
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

The typed full name is required for final signature evidence. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

  1. Go to Secure recipient link → Review & Submit.
  2. Find the record, endpoint, field or action used to type the e-signature full name.
  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

Workspace or endpointSecure recipient link → Review & Submit
PurposeThe typed full name is required for final signature evidence.

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 type the e-signature full name 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