Choose customer tools for application hosting plans

In the application product wizard or the plan's application settings, open Customer tools. The available profiles build on practical groups of hosting tools:

• Essentials includes core website tools such as domains, SSL, backups, site health, files, databases, database users, scheduled tasks, PHP and error information where supported.
• Business adds email and related tools, including forwarders, automatic responders and migration requests.
• Complete adds broader domain and account tools, including subdomains, aliases, redirects, DNS and disk information.
• Developer adds further technical tools such as PHP INI settings, FTP, email filters and deliverability controls.

WordPress products start with Business, while other applications start with Essentials. These are editable starting points, not immutable entitlements.

1. Select the profile closest to the plan's intended audience.
2. Read each enabled tool and remove anything your support team does not intend to provide for that plan.
3. Check server support and package permissions. A saved switch cannot create a missing provider capability.
4. Review optional CDN, ModSecurity, Terminal and Git availability. These are candidates on application plans and remain conditional on their own configuration and support.
5. Save the application settings, then reopen an active test service as a normal customer and verify the resulting interface.

General control panel login and hosting account password tools are excluded from application plans. Webmail can be available when the plan includes email. The Hosting Engineer's available tools are also filtered by the application plan, so a support feature should not be enabled merely to make an AI request succeed.

For older non-WordPress application products, the current compatibility behaviour can add essential tools needed to run the application until the settings are explicitly saved. Review and save your existing plans after upgrading so the stored tool choices reflect your intended product design.

Use a test client with ordinary permissions and check both visible controls and a harmless action. Then verify a restricted user cannot access management functions they should not have. A saved profile changes customer access; it does not migrate application data or upgrade the application's software. Communicate material tool removals before applying them to established customers.

• Choose hosting tools and limits for each product
• Configure Hosting Suite access rules and verify effective permissions
• Prepare customer Terminal access and verify SSH host identity
• Change, duplicate or convert an application hosting plan

• WHMCS service administration