•Using roles: Lock the account to prevent anyone from using it to connect to the server: 

ALTER USER ’old_app_dev’@’localhost’ ACCOUNT LOCK; 

Then treat the account as a role. For each developer new to the project, create a new account and grant to it the original developer account: 

CREATE USER ’new_app_dev1’@’localhost’ IDENTIFIED BY ’ new_password ’; GRANT ’old_app_dev’@’localhost’ TO ’new_app_dev1’@’localhost’; 

The effect is to assign the original developer account privileges to the new account. 

## 6.2.11 Account Categories 

As of MySQL 8.0.16, MySQL incorporates the concept of user account categories, based on the SYSTEM_USER  privilege. 

## System and Regular Accounts 

•System and Regular Accounts 

•Operations Affected by the SYSTEM_USER Privilege 

•System and Regular Sessions 

•Protecting System Accounts Against Manipulation by Regular Accounts 

MySQL incorporates the concept of user account categories, with system and regular users distinguished according to whether they have the SYSTEM_USER  privilege: 

•A user with the SYSTEM_USER  privilege is a system user. 

•A user without the SYSTEM_USER  privilege is a regular user. 

The SYSTEM_USER  privilege has an effect on the accounts to which a given user can apply its other privileges, as well as whether the user is protected from other accounts: 

•A system user can modify both system and regular accounts. That is, a user who has the appropriate privileges to perform a given operation on regular accounts is enabled by possession of SYSTEM_USER to also perform the operation on system accounts. A system account can be modified only by system users with appropriate privileges, not by regular users. 

•A regular user with appropriate privileges can modify regular accounts, but not system accounts. A regular account can be modified by both system and regular users with appropriate privileges. 

If a user has the appropriate privileges to perform a given operation on regular accounts, SYSTEM_USER enables the user to also perform the operation on system accounts. SYSTEM_USER  does not imply any other privilege, so the ability to perform a given account operation remains predicated on possession of any other required privileges. For example, if a user can grant the SELECT  and UPDATE  privileges to regular accounts, then with SYSTEM_USER  the user can also grant SELECT  and UPDATE  to system accounts. 

The distinction between system and regular accounts enables better control over certain account administration issues by protecting accounts that have the SYSTEM_USER  privilege from accounts that do not have the privilege. For example, the CREATE USER  privilege enables not only creation of new accounts, but modification and removal of existing accounts. Without the system user concept, a user who has the CREATE USER  privilege can modify or drop any existing account, including the root  account. The 

