The special disabled feature list is a server-wide restriction mechanism. It overrides ordinary feature lists, so a change here can affect accounts outside the particular reseller or package you were investigating.
IN THIS ARTICLE
What you need before you begin
Use this list only as an authorized server administrator applying a deliberate server-wide policy. Record the existing configuration and identify dependent customer workflows. For one package or customer, edit an ordinary feature list instead.
01 Use WHM disabled features for server-wide restrictions
- Open Packages > Feature Manager and select the predefined disabled list for editing.
- Locate the exact feature. This list has special semantics: selecting its checkbox disables that feature globally, even when ordinary lists enable it.
- Change only the intended entry and save. Do not assign the disabled list itself as the feature list for a customer package.
- Test accounts using more than one ordinary feature list to confirm the scope. Check dependent tools and customer documentation before considering the change complete.
- Record the reason and owner of the restriction so another administrator does not unknowingly re-enable it while troubleshooting an individual account.
How do I check that restricted features are unavailable?
Confirm the feature is absent from representative accounts and unrelated tools remain usable. Hiding a management interface does not necessarily disable an underlying server service or remove data already created through that service.
Troubleshoot unexpected results
If the change causes unexpected disruption, clear the global restriction you added and verify each affected ordinary list. If a feature is still missing afterward, inspect installed services, role permissions and package assignments. Do not alternate several global feature switches without keeping a clear record of what changed.
.png)
 (1).jpg)
 (1) (1).png)
 (1).png)
.jpg)
.jpg)
 (1).jpg)
.jpg)
