13 docs tagged with "global-settings"

Admins can open a live summary of portal billing configuration from the Billing Settings control on the admin Invoices page. The modal has three sections: Billing Mode, Enabled Global Settings, and Environment Flags.

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.

CMP exposes 200+ application-level flags under Admin Panel → Global Settings. Each flag controls platform-wide behaviour — registration fields, billing rules, login policy, and more.

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.

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.

These global settings control how long API login tokens stay valid. They apply to normal API TOKEN authentication — not long-lived REST API TOKEN tokens (see Notes below).

Marketplace Apps usually rely on an administrator startup script on the template. Customers may also enter their own startup script at deploy time. Both are combined into UserData sent to CloudStack, so size limits must be aligned.

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.

CMP includes admin-configurable rate limiting for support ticket creation and feedback submission. Limits control how many records a user can create within a configured time window.