Decide which server-management tasks your customers can perform from their WHMCS service page. PD AWS Lightsail has separate client controls, so you can offer direct server access, selected self-service tools or a service whose operational changes your team handles.

Choose the controls for your offering

• Client: Start, Client: Stop and Client: Reboot control the corresponding power actions separately.
• Client: Connection details lets customers view the connection information supplied for their server.
• Client: Firewall provides the customer firewall controls.
• Client: Snapshots provides the manual snapshot controls, including restore and deletion. Enable it when customers should manage their recovery points, not just view backup information.
• Client: Usage graphs provides the customer usage charts.
• Client: Console controls the optional browser terminal. It also needs the module-wide console setting enabled and an eligible service; see the browser-console guide.

Save the product settings

1. Open System Settings → Products/Services → your product → Module Settings and edit the Lightsail product.
2. Find the module's Client: settings.
3. Enable the controls included in this offering and disable those your team will manage instead.
4. Save, then reopen the product to confirm your choices were retained.
5. Review an appropriate service's customer view and compare its available actions with your choices.

A power action can be unavailable because of the server's current state. Check that state before treating a disabled button as an unsaved setting. You do not need to stop, reboot or restore a customer's server simply to check which controls are offered.

Example: access without customer-managed recovery

Suppose customers need SSH connection information and usage charts, while your team handles firewall changes and snapshot recovery. Enable Client: Connection details and Client: Usage graphs. Disable Client: Firewall and Client: Snapshots, then decide individually whether customers should start, stop or reboot the server.

This is one possible service design. Disabling client-area controls does not revoke access a customer already has through SSH or another separate route. Describe the service you actually provide rather than treating hidden buttons as a complete access policy.

Confirm the customer experience

Check that the intended service page shows the tools included in the offering. Read the welcome email and product description too: they should not promise customer firewall or snapshot management when those controls are disabled.

For the individual tasks, see SSH connection details, firewall rules and manual snapshots.