Britixo CRMBritixo CRM Enterprise Help Centre
Help centreClient Discovery & Project Briefing PortalResolve missing signature consent
Review, e-signature and final submission

Resolve missing signature consent

Select the final confirmation checkbox.

Audience: CRM administrators, project teams, developers, authorised client contacts and public prospectsPermission: Secure-link recipientModule v1.1.1
Exact navigationSecure recipient link → Review & Submit
Before you begin
  • Confirm 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 covers

Select the final confirmation checkbox. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Open Secure recipient link → Review & Submit.
  2. Locate the record, endpoint, field or action used to resolve missing signature consent.
  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, choices and supported possibilities

Workspace or endpointSecure recipient link → Review & Submit
PurposeSelect the final confirmation checkbox.

Code-backed validations and workflow rules

  • 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.

Expected result and verification

  • The resolve missing signature consent 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.
Resolve missing drawn signatureOpen the thank-you pageReview, e-signature and final submissionBrowse all Client Discovery & Project Briefing Portal guidesClient portal overviewAdd and manage customer contactsConfigure customer contact permissionsUpload and share customer filesConfigure SMTP email deliveryReview email delivery issues