An account overview
Dashboard cards surface active services, unpaid invoices, open tickets and balance. Customers can move from the summary to the relevant detail page instead of treating an email notification as the only record of their account.
The LucidCP hosting client portal connects services, domains, invoices and support in a customer workspace. Customers can follow an order after checkout, find their next payment and open a ticket linked to the service that needs attention.
A customer should not need to ask support where an invoice is, whether a service has activated or where to change nameservers. The portal groups these tasks around the signed-in account. Each service keeps the controls its connected module supports, while commercial history remains in the same workspace.
Dashboard cards surface active services, unpaid invoices, open tickets and balance. Customers can move from the summary to the relevant detail page instead of treating an email notification as the only record of their account.
My Services leads to the product, service status, billing cycle and available controls. A hosting service and a VPS can expose different actions. Supported modules may offer panel access, power controls or other operations; check the exact integration for the available set.
My Domains groups the customer’s domain records and supported registrar controls. Nameserver changes, renewal settings and transfer-related actions depend on the connected registrar. A domain purchase and hosting account remain separate services even when the customer orders them together.
Customers can open an invoice, review its items and due date, and choose from enabled payment methods. Balance and saved payment options are available when configured. After provider checkout, the invoice status is the place to verify that a payment was recorded.
A ticket can include the affected service, department, subject and conversation history. This gives the support team a clearer starting point and gives the customer one thread to follow. The knowledge base provides another route for questions already answered by the provider.
Review the available storefront and client-area themes, then choose the design that suits your offer. Language, currency and advanced options depend on the selected license and configuration. Preview the actual pages on desktop and mobile before opening the store.
Use a test customer to check the same path a buyer will take. Verify what appears before payment, during activation and after the service becomes available.
The customer browses Store, selects a product and completes any displayed domain, configuration or add-on fields. Product settings determine which choices are available.
Checkout should clearly show the billing period, amount and applicable options. The customer chooses an enabled method and completes the provider’s payment flow.
The order moves through your configured provisioning or approval workflow. The customer opens My Services to review the result rather than placing another order while activation is pending.
The customer returns to the portal for invoices, renewals, domains, profile information and supported service commands. Review sensitive operations and their consequences before using them.
If something fails, the customer opens a ticket and selects the relevant service. An invoice reference, error message and expected outcome help the team investigate the same account history.
Admin access is useful for configuration, but it does not prove that a customer can complete the workflow. Validate a test customer’s view after product, payment, theme or integration changes.
No. The client portal manages the customer’s relationship with your hosting business: orders, services, invoices and support. A hosting control panel manages the hosting account itself. Supported integrations connect the two experiences and may provide panel access.
No. The available operations depend on the virtualization module, product configuration and service state. Review the integration’s customer view for the exact controls instead of assuming that every platform includes console, reinstall, snapshots or networking features.
Customers can inspect invoices and pay through methods you enable. Account balance and saved payment options depend on your configuration. Exceptions such as an unmatched provider payment still need staff review; the invoice and transaction references help resolve them.
The customer interface is responsive. Your selected theme, content and enabled modules still need an end-to-end mobile check, especially checkout, service commands and longer support forms. The public theme showcase helps you compare the available designs.
Explain where to find services, invoices and support, then link to the relevant help articles from your onboarding material. Use a controlled customer account to verify the instructions. Review account data and access settings before inviting customers to use a new installation.
Hi! Need help with plans, installation, or licensing?
Help Center Open a Support Ticket Integrations