Remove an additional MySQL login when it is no longer needed. Applications using that login will lose access, so identify and migrate them before removal.

Open the intended service

Sign in to the client area, open Services → My Services, select the intended MySQL service and open its module management page. Confirm the service and resource before making a change. Enable the corresponding client feature on the intended offering. If a section is missing or unavailable, review that service’s configuration rather than trying a different service.

Identify the exact login

Open Database Users, or Manage users from the overview. Check the username against the application’s configuration and any other integrations using the account. Arrange a replacement login and test it first if access must continue.

This page shows usernames without their separate MySQL host values. If the same name exists for more than one host, do not guess which account will be removed; identify the exact account and handle it through the appropriate database administration process. System/admin accounts are excluded from this customer list.

Remove the intended user

1. Confirm the applications that use the login have been updated or are intentionally being retired.
2. Find the exact row and choose Remove.
3. Read the confirmation explaining that applications using the login will lose access.
4. Confirm only when that interruption is intended. Wait for completion and reload the list.
5. Check that replacement application connections work and that the removed login can no longer be used as intended.

Removing a user is different from deleting an application database. Do not use a user-removal result as proof that the database or its contents were removed.

Check the outcome

Wait for the provider operation to settle, then reload the relevant section and verify the actual result. A success notice or Done activity row can precede final provider completion. If an operation is already in progress, wait rather than repeatedly submitting it.

An empty list can also result from a failed read; it does not establish that the resource has no entries. For an uncertain result, reconcile the service and provider state before repeating a change. Do not include passwords, provider keys or full customer records.

See the PD Google Cloud MySQL WHMCS guide for related setup, or explore PD Google Cloud MySQL.