12 docs tagged with "registration"

Prospective affiliates sign up through a public registration link. After they complete the flow, the request is sent to the admin for approval — the affiliate account is not active until an admin approves it.

When a customer is registered in CMP (admin onboarding or self-registration, depending on your payment mode), CMP registers them in OpenStack using the admin connector, then switches to the customer's own credentials for all later API calls.

Enable Mobile Verification controls whether CMP triggers SMS OTP verification for customer mobile numbers during registration and when updating mobile numbers from the customer profile.

Enable Phone Input is the primary global setting for phone number fields across the platform. When it is off, all phone inputs — billing phone, profile phone, signup phone, and related fields — are hidden.

When one-liner mode is disabled, use this flag to require (or allow skipping) acceptance of the full in-product Terms and Conditions.

Enforce Mobile Verification dictates whether completing mobile number OTP verification is mandatory (compulsory) or optional for customers to finish onboarding.

Hide Billing Phone removes the billing phone number field from organization and billing forms. It applies only when enable_phone_input is also enabled (true).

Hide Postal Code removes the postal / zip code field from all applicable forms. When enabled, users are not prompted for a postal code and can complete registration, onboarding, and billing updates without it.

In this approach, the full Terms and Conditions are shown inside the registration flow (for example the Accept T&C step after email verification and payment). Customers review and accept without leaving CMP for an external website.

One-liner Terms and Conditions shows a checkbox on the frontend Signup form. The label includes a link that opens the provider’s public Terms and Conditions page in a new browser tab.

CMP supports sending transactional SMS messages — including one-time passwords (OTP) for mobile verification during customer registration — through external SMS service providers.

CMP can require customers to accept Terms and Conditions during signup and onboarding. Admins choose how terms are shown (external link vs in-product content) and whether acceptance is mandatory.