You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, clients are required to log directly into the panel to make changes. The configuration in FossBilling primarily serves informational purposes, leaving clients with limited control over their services unless the client uses the panel itself.
Describe the solution you'd like
I propose a solution where clients can easily manage various services such as email (mailboxes, aliases, etc.), FTP accounts, site settings (PHP version, SSL certificate renewals, custom vhost settings, etc.), and DNS management (creating, deleting, and modifying assigned zones). This would provide clients with a more intuitive interface for managing their services. Currently, clients are forced to access the backend, which can be confusing for novice users and may lead to accidental changes that require the provider to intervene and revert.
Describe alternatives you've considered
Currently, there are no other viable alternatives to this approach.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, clients are required to log directly into the panel to make changes. The configuration in FossBilling primarily serves informational purposes, leaving clients with limited control over their services unless the client uses the panel itself.
Describe the solution you'd like
I propose a solution where clients can easily manage various services such as email (mailboxes, aliases, etc.), FTP accounts, site settings (PHP version, SSL certificate renewals, custom vhost settings, etc.), and DNS management (creating, deleting, and modifying assigned zones). This would provide clients with a more intuitive interface for managing their services. Currently, clients are forced to access the backend, which can be confusing for novice users and may lead to accidental changes that require the provider to intervene and revert.
Describe alternatives you've considered
Currently, there are no other viable alternatives to this approach.
The text was updated successfully, but these errors were encountered: