PanelAlpha Documentation
Back Home
Live Demo Get Started

Quick Onboarding

Documentation
    Introduction FAQ
Getting Started
    Requirements Installation Update Guide SSL Configuration Resetting Admin Password Translations Health Check
Admin Area
    Dashboard Instances Services Users Logs Migrations
Onboarding Methods
    Quick Onboarding Super Quick Onboarding Standard Onboarding
System Configuration
    General Configuration Branding Hosting Servers DNS Servers Email Servers Remote Backups Plans Notifications Automatic SSL Themes, Plugins and Packages
Hosting Server Connections
    Hosting Scenarios PanelAlpha Engine for Docker cPanel Plesk DirectAdmin WP Cloud
Email Server Connections
    Mailcow cPanel
DNS Server Connections
    Cloudflare cPanel DNS Only PowerDNS
Billing Systems Integrations
    WHMCS
Billing Scenarios
    Introduction Single WordPress Instance Predefined WordPress Template Multiple WordPress Instances Cross-Selling Paid Plugins and Themes Cross-Selling Domains Plan Upgrade Free Trial Period
Integrations
    Integrated Solutions Matomo Google Analytics Let's Encrypt Google PageSpeed Insights DB-IP Extendify
Client Area - Instances
    List of Instances Creating New Instance Importing Existing Instance Instance Details Changing Domain Sharing Instances Monitoring Backups Plugins Advanced Settings
Client Area - Hosting
    Summary Domains FTP Accounts MySQL Databases Cron Jobs DNS Zone Editor Email Addresses Email Forwarders

# Quick Onboarding

The Quick Onboarding method allows the PanelAlpha end users to create new WordPress instances in a fast and easy way. The entire process can be minimized to just two steps: that is selecting a theme for your website and then entering the site name. No additional configuration is required to create a basic yet fully functional website ready for management.

Underneath, in the Workflow section, you will find a step-by-step description of the process, including optional configuration aspects that may be skipped if not set as required.

Try out the free trial in your billing system, like WHMCS. It can help boost conversion rates.

# Configuration

To offer your end-users the option to create websites in a quick manner, you must offer a service with a plan with the quick onboarding method assigned. Let's start from creating a plan:

  1. Navigate to the admin panel: Configuration → Plans and press the Add button.
  2. Proceed to the second step of the plan configuration: Onboarding, there select the Quick Onboarding method.
  3. Configure the Quick Onboarding method options:
    • Use Template For New Sites - Select one template that will be used by default for creating websites, now you may also let the clients choose a theme that will be installed with the template; if left empty, clients will not have the option to create websites based on existing instance template.
    • Force installation for new users after login - If selected, the first step after logging into the PanelAlpha client area for new users will always be creating a new instance (this option is recommended and selected by default). If unchecked, creating a new website will be triggered by the end-user manually by pressing the "Add New" button in the client area main page.
    • Ask for domain - If selected, clients will be asked to provide a domain before the instance is created (this option is selected by default). If not selected, additional configuration fields will appear. The domain will be automatically generated based on the configuration below:
    • Domain used for subdomains - Enter the main domain to allow creating subdomains. You will also need to set up a wildcard in the DNS server to ensure that the pages are correctly accessible.
    • Automatic subdomain format:
      • Friendly name based on website name - The subdomain will be generated based on the provided website name, for example: john-blog.mydomain.com
      • Friendly name random combination - The subdomain will be randomly generated, for example: purplegoose.mydomain.com
      • Specified number - Enter description and the next number based on which a subdomain will be generated, for example: "temp{number}", "100000": temp100000.mydomain.com
      • Random length - Enter the number of signs to generate a subdomain, for example: "10": 4d7wg9r98x.mydomain.com

# Workflow

Now that a plan is ready, let us show you how it is used in practice.
You must be aware that the below-illustrated flow is just an example and the flow might vary depending on the number of services owned by the client, assigned to them plans, and their specification!

  1. The end-user, after successfully purchasing a service in your billing system (for example: WHMCS), is redirected to the PanelAlpha client area via SSO.

  2. If the Force installation option has been selected, the instance creation is triggered immediately. Otherwise, the client has to manually start creating the website: "Add New" → "Create New WordPress Instance" → "Continue."

  1. Next, the client has to select a product (in our case, "Basic" for Quick Onboarding illustration). Note that this step will be skipped if the client owns just one service!
  1. If the Ask for domain option has been selected, the client has to provide a domain name for their new website now. Otherwise, the client will be moved to the theme selection page, the selected there theme will be used for the website installation.
  1. It is time to provide a name for the new website. It's important to note that the domain will be created according to the plan configuration, specifically with "Automatic subdomain format" → "Friendly name based on website name" in our example.
    The domain can be easily changed later on after the site is installed by using the "Change Domain" button in the instance details.
  1. Please now wait until the site installation is successfully completed. This process might take a while.

Important!

  1. If a client has numerous services, and all of them require a theme, the flow will be as follows:
    Choose theme → Select product → Provide domain (if required) → Provide instance name.
  2. If a client has numerous services and only some of them require a theme, the flow will be as follows:
    Select product → Choose theme (for those products that require it) → Provide domain (if required) → Provide instance name.