Repository navigation
[Feature Request / Security] Distinguish Admin vs. User Domain Suspensions and Add Custom Suspension Pages #1166
Closed
justiceakorede
started this conversation in
Ideas
Replies: 2 comments
|
nice ideas! I'll implement the different templates option so admin can create as many as they want), and add more checks to ensure when admin suspends a domain it cant be worked-around by the user. for now, to avoid users re-enabling suspended domains just disable the suspend_domains module. |
0 replies
|
added in testing for 2.0.16 - thanks for the suggestion! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Currently, both Admins and Users share the exact same permissions when suspending domains.
If an Admin suspends a domain for critical policy violations (e.g., copyright infringement, malware, DMCA, or phishing), the account user can simply log into their control panel and click Unsuspend, completely overriding the administrative action (when suspend domain module is enabled for users).
While the "Domain Suspension" module is a great self-service feature for users (e.g., web developers temporarily disabling a client's site for non-payment), user actions should never override root administrative decisions.
Suggestion
Currently, OpenPanel only supports 3 default pages:
It would be extremely beneficial to allow custom templates for domain suspensions so administrators can select specific reasons, such as:
Additional Context
Adding a permission hierarchy for domain suspensions prevents malicious or non-compliant users from putting the server/IP reputation at risk by re-enabling dangerous content after an admin intervention. Custom template support also improves clarity for visitors when a domain is taken down for a specific legal or administrative reason.
All reactions