Control package applications and advanced features
Decide which application, WordPress, backup, DNS, PHP, SSH, SSL and Redis controls a subscribed customer receives.
Where Settings → Packages → package → Applications / Backups / Features
What this is for
- Apply least privilege through package design.
- Standardise WordPress and PHP defaults.
- Allow self-service only where operationally supported.
Before you start
- List the support and security implications of every self-service feature.
- Check that required PHP versions, Redis and backup services exist on the target servers.
Steps
-
1
List the customer journeys and support commitments for the package.
-
2
Allow only the application installers and WordPress management actions customers need.
-
3
Choose whether customers can view automatic backups, create manual backups and self-restore.
-
4
Choose whether customers may install custom SSL, use SSH, clone websites or edit php.ini.
-
5
Restrict supported PHP versions to releases available and supported by your server estate.
-
6
Enable Redis only when the package and target servers support it.
-
7
Test the package through a subscribed demo customer before selling or migrating it.
Check it worked
- A demo customer can use every enabled feature and cannot see disabled features.
- Website creation, backup access, SSL, SSH, PHP and Redis match the published package description.
Tip
A smaller, well-tested feature set is easier to support than enabling every control by default.
What the controls do
| Control | What it means |
|---|---|
| WordPress managers | Allow customer control of plugins, themes, users and admin lockdown. |
| Self restore | Allows customers to restore files, mailboxes or complete websites. |
| Supported PHP versions | The runtime choices visible for websites using the package. |
| Allow Redis | Makes the optional Redis service available to subscribed customers. |