URL where issue was found:

https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.14/html-single/installing_red_hat_3scale_api_management/index#external-databases-installation

Oracle specific user permissions are documented here: https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.14/html-single/installing_red_hat_3scale_api_management/index#configure-database-user

MySQL specific permissions are documented here: https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.14/html-single/installing_red_hat_3scale_api_management/index#configure-external-mysql-database

PostGRE specific permissions are not documented.

Description of issue:  

Current  documentation does not provide any details about if the permissions/privileges the 3scale user db needs for installing 3scale are the same to the ones that are required for operating 3scale during the daily ops. In other words, know whether 3scale installation/upgrades requires higher privileges than day to day ops so if that is the case, a regular user with less privileges can be created for the day to day 3scale ops.

Many companies worry about security issues about too_many_permissions for database users. Therefore, they are looking to grant db users with just the minimal required permissions/privileges required for each deployment status (installing/upgrading versus.  day to day ops). 

It would be nice if the 3scale doc can address these concerns by detailing the permissions/privileges the 3scale db user will need for:

a) 3scale API Management installation/upgrades

b) Day to day 3scale API Management work  ( e.g. may be for the installation it is required P1, P2, P3 and P4 permissions but once the 3scale it's installed/upgraded, then the required permissions to operate 3scale during the day to day could be only P1).