We moved this page to our Documentation Portal. You can find the latest updates here. |
Question
How can I hide pricing and billing information from my OnApp Control Panel?
Environment
All OnApp Versions
Resolution
- OnApp 5.9 and subsequent versions:
If you run your cloud on OnApp 5.9 and later versions, you can Disable Billing at your Control Panel > Settings > Configuration > System. This option allows to hide all the billing-related information from users in your cloud. - Versions prior to OnApp 5.9:
If you run your cloud on any version prior to OnApp 5.9, you can disable the billing-related permissions via the Roles and Sets menu.
Here is a list of permissions that you may want to disable for users. Not every permission may be necessary and some of them are disabled by default for users who are not administrators:
Any action on billing plans
Create a new billing plan
Delete any billing plan
See list of all billing plans
See details of any billing plan
See own billing plan
Update any billing plan
See user billing plan
Full access to user group monthly bills statistics
See all user group monthly bills statistics
See only own user group monthly bills statistics
Any action on company billing plans
Create a new company billing plan
Delete any company billing plan
See details of any company billing plan
See own company billing plan
Update any company billing plan
Read price for all Edge Group Locations
Update price for relation group template
See all users prices
See user backups/templates prices
See user billing plan
See user hourly prices
See user monthly prices
See user outstanding amount
See user summary payments
See user virtual server prices
See user total costNote: If "Any action on X" or "Full access to X" are set to "Yes", they will override all the other settings in their respective categories. Make sure that they are set to "No", if you want to manage specific permissions within a Role.
After you edit permissions, be sure to save your changes. Users should no longer be able to see pricing as long as you have set the appropriate permissions to "No".