Identify whether you are renaming an additional FTP user or the subscription main system user. Record its home directory and permissions. A system-user rename can affect more services and filesystem paths than renaming a limited FTP account, so review dependent jobs first.

1. For an additional FTP account, open FTP Access for the domain and select the username. For the subscription system user, open Web Hosting Access.
2. Review the editable username field and enter a valid unique replacement. Follow the character restrictions shown by Plesk.
3. Check that the home-directory restriction and other permissions remain appropriate. If this is a security handover, rotate the password as a separate part of the same planned change.
4. Save the account and update all authorized transfer clients, deployment secrets and scripts that reference the old login.
5. Test a new encrypted connection with the replacement username. Review any job that contains a hard-coded home-directory path after a system-user change.

Confirm the intended directory is accessible and unrelated directories remain restricted. Verify a controlled file transfer and the next scheduled deployment. Check that old client profiles have been updated or retired.

If the name is already used, choose another valid name rather than removing an unrelated account. If a system-user rename is unavailable or affects a managed application, ask support about the supported process. Do not manually rename operating-system users or directories from a shared-hosting account to imitate the panel action.

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

• Plesk: Changing FTP Access Credentials
• Plesk: Adding FTP Accounts