For example, user A is granted with the permission to delete the testdb database. Delete the database and create another one with the same name. You need to grant user A the deletion permission of the testdb database again.
Permissions can be granted to new users or projects, modified for users or projects with existing permissions, or revoked from a user or project.
Parameter |
Description |
---|---|
Authorization Object |
Select User or Project. |
Username/Project Name |
|
Non-Inherited Permissions |
Select a permission to grant it to the user, or deselect a permission to revoke it. Non-inherited permissions apply only to the current database.
|
Inherited Permissions |
Select a permission to grant it to the user, or deselect a permission to revoke it. Inherited permissions are applicable to the current database and all its tables. However, only the query permission is applicable to table columns. The following permissions can be granted to both user and project.
|
For a user or project that has some permissions on the database, you can revoke the existing permissions or grant new ones.
If the options in Set Permission are gray, the corresponding account does not have the permission to modify the database. You can apply to the administrator, database owner, or other authorized users for granting and revoking permissions of databases.
In the Project Permission Info list, locate the project for which you want to set permissions and click Set Permission.
For details about the permissions of database users or projects, see Table 1.
If a user is an administrator, Revoke Permission is gray, indicating that the user's permission cannot be revoked.