Editing and permissions of MySQL and MariaDB database users

Form for editing user data and rights:

Change of login data.

Choose an authentication plugin

Choose a proxy account.

Specification of maximum queries, updates, connections per hour,
as well as the maximum user connections and the maximum execution time of SQL scripts. 0 = unlimited.

The encryption for connections can also be specified.

Assignment of global permissions:

Data Permissions.

Structure Permissions.

Administrative Permissions.

Taking over permissions by assigning permission roles.

Take over rights from: Copy permissions from another user account.

All: Also copy object permissions (database, tables, views, routines) from another user account.

Test: Connection test for the user account.

Save changes: Login data and global permissions are saved.

Databases, tables, columns, views, procedures, functions: Assignment of permissions for database objects.
Changes are applied immediately at the object level without pressing Save changes.

Representation and editing of user permissions at database level.

Permissions can be set individually.

All permissions for an object can be set or revoked with one click.

One permission can be set or revoked for all databases with one click.

Global rights: The permissions are determined on the global level. Switching off causes the rights to be copied from the global level to the database level.

Display and editing of user permissions at table level.

Selection of database.

Tables can be filtered by alphabetical selection or keyword.

Permissions can be set individually.

All permissions for a table can be set or revoked with one click.

One permission for all tables can be set or revoked with one click.
Depending on the number of tables, the process may take longer.

Parent rights: The rights are determined by parent levels (global, database). Switching off causes the permissions to be copied from the parent levels to the table level.

Display and editing of user permissions at table column level.

Selection of database.

Selection of the table.

Permissions can be set individually.

All permissions for a column can be set or revoked with one click.

One permission for all columns can be set or revoked with one click.
Depending on the number of table columns, the process may take longer.

Parent rights: The rights are determined by higher level (global, database, table). Switching off causes the rights to be copied from the higher level to the table column level.

Representation and editing of user permissions at view level.

Selection of database.

Permissions can be set individually.

Views can be filtered by alphabetical selection or keyword.

All permissions for a view can be set or revoked with one click.

One permission for all views can be set or revoked with one click.
Depending on the number of views, the process may take longer.

Parent rights: The permissions are determined by higher level (global, database). Switching off causes the permissions to be copied from the higher level to the view level.

Display and editing of user permissions at procedure level.

Selection of database.

Permissions can be set individually.

Procedures can be filtered by alphabetical selection or keyword.

All permissions for a procedure can be set or revoked with one click.

One permission for all procedures can be set or revoked with one click.
Depending on the number of procedures, the process may take longer.

Parent rights: The permissions are determined by higher level (global, database). Switching off causes the permissions to be copied from the higher level to the procedure level.

Representation and editing of user permissions at function level.

Selection of database.

Permissions can be set individually.

Functions can be filtered by alphabetical selection or keyword.

All permissions for a function can be set or revoked with one click.

One permission for all functions can be set or revoked with one click.
Depending on the number of functions, the process may take longer.

Parent rights: The permissions are determined by higher level (global, database). Switching off causes the permissions to be copied from the higher level to the procedure level.