Confirm the exact username and whether any active deployment or backup job uses it. Identify the account owner and record its directory restriction if you may need to recreate equivalent access later. Do not confuse an additional FTP user with the subscription main system user.

1. Open the domain FTP Access page and find the additional account.
2. Check its username and home directory against the access record. Move any legitimate automation to a tested replacement before removal.
3. Select the intended account and choose the remove action. Read the confirmation and ensure it concerns the FTP account you intend to retire.
4. Confirm removal, then remove the retired credential from deployment settings and password records according to your access-management process.
5. Review other access granted to the same person, such as panel users, SSH keys or repository tokens, if this is a complete offboarding.

Confirm a new connection using the retired credential fails while the website and other authorized transfer accounts still work. Check the next scheduled job to ensure an overlooked dependency is not repeatedly failing.

If the account cannot be removed, check whether it is the main subscription system user or a managed dependency. Do not delete the subscription to revoke one person access. For accidental removal, create a new restricted account with the required directory and permissions, issue a fresh password and update clients; do not assume the old account settings can be recovered automatically.

• Creating a restricted FTP account in Plesk
• Changing an FTP or subscription system-user password in Plesk
• Changing an FTP username in Plesk

• Plesk: Adding FTP Accounts
• Plesk: FTP Access To Your Websites