76 docs tagged with "platform"

The client account exists but the user cannot log in and status stays Pending. Is there an approval dashboard?

Create catalogue items under Settings → Products → Products → Add Product.

Affiliate documentation is still in progress. Pages may be incomplete or updated as the module evolves.

After an admin approves their account, affiliates log in to the affiliate portal at /affiliate/login.

Open an active affiliate from Affiliates → Manage Affiliates → Active Affiliates to manage account data, referrals, commissions, and settings.

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.

End-to-end flow from affiliate registration through customer referral, commission, and payout.

CMP is built on REST-based APIs. Use this page to enable API access, generate tokens, authenticate, and configure role-based permissions for integrations.

When a customer deploys a VM from a Marketplace App, CMP can send an email with application credentials and environment details (for example WordPress admin URL, username, and password) — not only the generic “VM created successfully” message with OS, RAM, and storage.

Product guide: Two-factor authentication.

Auto Pay automatically purchases infra credits when an account’s available balance falls to or below a configured threshold. That helps prepaid customers keep services running without manually topping up every time the wallet runs low.

CMP automates infrastructure provisioning — virtual machines, storage, and networking. Application-level automation depends on what runs inside the guest OS and what you explicitly pass through Marketplace environment variables and startup scripts.

Concept-only answers. Full comparison: Backup and Recovery.

Platform Q&A for pay-as-you-go, invoices, pricing formulas, snapshot charges, and tax. Full product guides: Billing overview, Pricing formulas.

Billing for a product starts immediately when the order is placed. CMP uses the configured payment type, billing cycle, and billing rule. No separate activation step is required for billing to begin.

How can a provider add external document URLs from their own website?

CMP can protect customer portal forms (login, registration, and similar) from spam and automated bot submissions using CAPTCHA providers.

Categories organize products in CMP and drive category tabs in the customer Store (for example Backups, Support).

Path: Report → Commissions

Path: Settings → Orchestrator → Apps Marketplace

This section documents customer-facing areas of the CMP portal — what end users see on the Dashboard, under Profile, Billing, Quota, and related menus.

Customers purchase standalone products from the Store in the customer portal.

The affiliate Dashboard is the home page after login at /affiliate/login.

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.

During Marketplace App deployment, some application settings must be configured dynamically — for example username, password, database name, or site URL for a WordPress or PostgreSQL image.

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.

CMP supports Google reCAPTCHA v2 Checkbox to protect forms from spam and automated bot submissions.

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.

CMP supports Keycloak as an external identity provider for SSO, social login (Google, GitHub), and 2FA when Keycloak is the active provider.

Admins review affiliate registration requests, approve accounts, and manage active affiliates.

Marketplace apps are VM templates with pre-installed applications. The service provider prepares the image (OS + application) so end users can deploy a ready-to-use app without installing software manually.

This document lists the mandatory configuration details required to enable CMP to send transactional SMS messages (such as registration verification OTPs) via MSG91.

CMP can present the customer (end-user) portal in multiple languages. Multi-language is disabled by default (English only) until the StackConsole team enables it for your deployment.

CMP notification system for customer and admin alerts — email (and related channels), event-driven messages, and notification preferences.

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.

When a customer places a product order, CMP:

Path: Report → Payouts

This section covers CMP-level capabilities that are not tied to a single orchestrator — APIs, notifications, store/marketplace, and other cross-cutting product features.

Questions about CMP product behaviour — billing, branding, auth, accounts, and packaging — that apply regardless of which orchestrator is connected.

Wallet top-up, free credits, coupons, and free trial. Product guide: Prepaid.

Configure product prices on the rate card after the product exists.

Vendors identify who supplies a product (procurement, support contacts, reporting).

What cloud provider administrators need before enabling StackAI in a production CMP deployment.

This page lists what is new in Products / Store. Most of the Store & Products documentation describes capabilities that were not available before this release.

Configure affiliate programs, commission rules, payout methods, and taxation before and after affiliates register.

How CMP charges public IPs vs VPC / isolated / shared network packages. Feature context: Isolated Network, VPC Network, Shared Network, IP Address (CloudStack) · IP Address (Proxmox).

Customers can review how much quota their account is using and sync usage when reported numbers do not match their live services.

Path: Report → Referred Signups

CMP supports Reseller and Vendor partner account types in addition to end Customers. Resellers get a white-labeled portal and control customer billing; vendors onboard customers on the provider portal and are billed for aggregated customer usage.

This page covers provider (super admin) → reseller billing and reseller → reseller’s customer billing, plus vendor billing notes and current limitations.

Use this page to choose the right partner model and explain differences to providers and partners.

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

StackConsole implements multiple layers of security and fraud prevention across the application, authentication, API, network, billing, and infrastructure layers.

How do we change the default date-time format for the application and for an account?

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

This document describes the configuration parameters required to enable transactional SMS delivery and mobile verification in CMP using the Spinning Disk SMS Gateway.

StackAI is in beta. Capabilities, suggested prompts, and enabled tools may vary by tenant. Confirm with StackConsole which features are active on your deployment.

What's live today, what we're building now, and what's planned next.

A practical tutorial for managing your cloud with natural language.

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.

This documentation describes an improvement on the basic Products / Store feature. It is not yet rolled out to all deployments — you may find that some of these capabilities are not available on your CMP today. They will become available in upcoming updates.

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.

This document lists the mandatory configuration details required to enable CMP to send transactional SMS messages (including registration verification OTPs) globally via Twilio.

CMP provides two-factor authentication (2FA) to secure accounts with an extra verification step during sign-in.

What is user enumeration?

Override root disk, free OS disk, scheduled stop, and related packaging choices. CloudStack offering mapping: Virtual Machine packages.

Create a Zitadel service account (machine user) and Personal Access Token (PAT) so CMP can create or link users during user migration.

Zitadel integration is currently in Beta. It is fully functional for OIDC customer/affiliate authentication and user migration, with continuous enhancements being added.

Step-by-step setup for a Zitadel instance, Stack Console Web/OIDC application, and CMP Social Login configuration.

When transitioning to Zitadel, existing CMP accounts can be migrated so that users can seamlessly sign in through Login with Zitadel using their registered email addresses.