Identify the full FTP username and directory scope. Confirm no current deployment, backup or collaborator still relies on it. Keep a record of the access being retired and review any option that might also remove files.

1. Open Account Manager > FTP Management.
2. Select only the additional account to retire. The main hosting account is not a disposable subordinate FTP user.
3. Choose Delete and read the confirmation, especially any file-removal options. Do not agree to delete a shared website directory when you only intend to remove login access.
4. Confirm removal and update authorized deployment or automation configuration so it no longer attempts this login.
5. Review separate panel users, SSH keys, SFTP access and application administrator accounts belonging to the same departing collaborator. They are not automatically revoked by deleting an FTP user.

Review the FTP username and its home directory before deletion. Confirm the incoming maintainer has a separate authorised way to access the required files.

Read the removal confirmation carefully, especially any option affecting the associated directory. Do not remove live files simply because the FTP login is no longer needed. Keep a backup and a record of the path before proceeding.

What should the verification include?

Test a new connection with the retired login, check the website through its public hostname and confirm legitimate uploads still work using the replacement access. Review automated tasks that may have relied on the old credential.

If the removed user also had DirectAdmin, application, Git or database access, review those separately. One account-removal action does not establish that every access route is closed. Contact our team when you are unsure which object owns a directory or which credential a deployment job uses. Share the username, path and relevant error, but keep passwords, private keys and deployment secrets out of the ticket.

Confirm the account is absent and a fresh connection with that identity is denied. Verify the website files and public application still work as expected, and check for broken scheduled jobs.

If the wrong account was deleted, recreate a properly scoped replacement with a new unique password and update its legitimate users. Do not reuse a potentially exposed secret. If files were accidentally removed too, stop unnecessary writes and recover from the verified backup through an authorized restore process.

• Creating a restricted FTP account in DirectAdmin
• Changing an additional FTP account password in DirectAdmin
• Suspending or re-enabling an FTP account in DirectAdmin
• Creating and downloading a full DirectAdmin account backup

• DirectAdmin Evolution: FTP