Britixo CRMBritixo CRM Enterprise Help Centre
Help centreProplix Secure API GatewayComplete login email
Portal login, registration and password reset

Complete login email

Use the client contact email.

Audience: CRM administrators, integration developers, external portal backend teams and security reviewersPermission: Valid active master portal tokenModule v1.0.0
Exact navigationExternal backend → Proplix API Gateway portal account endpoints
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

Use the client contact email. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Open External backend → Proplix API Gateway portal account endpoints.
  2. Locate the record, endpoint, field or action used to complete login email.
  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 endpointExternal backend → Proplix API Gateway portal account endpoints
PurposeUse the client contact email.

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 complete login email 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.
Use POST for portal loginComplete login passwordPortal login, registration and password resetBrowse all Proplix Secure API Gateway guidesEnterprise integrationsClient portal overviewApply API request throttlingUnderstand one-way API-token storageManage API-token lifecycle metadataData, privacy and security