An additional FTP account gives a developer file access without sharing the subscription main system-user password. Restrict it to the directory needed for the task. FTP accounts do not automatically provide SSH or SFTP access, because those services use a different authentication and permission model.
IN THIS ARTICLE
Check access and requirements
Confirm your subscription allows additional FTP accounts and identify the intended directory. Prefer encrypted FTPS with the verified server hostname. Decide whether the person needs to upload changes or only retrieve files, using the permissions supported by the server platform.
01 Create a restricted FTP account in Plesk
- Open the domain FTP Access page and choose Add an FTP Account.
- Enter a distinct username and a unique strong password. Avoid sharing one developer account among unrelated people.
- Select the home directory carefully. Limit it to the required website or project directory rather than the whole subscription when broader access is unnecessary.
- On Windows, review the available read and write permissions. On other platforms, confirm the directory restrictions and supported permissions for the account.
- Save the account and configure an FTP client with the verified hostname, full username and FTPS settings supplied for the server. Confirm the certificate before connecting.
How do I verify the FTP account is restricted correctly?
List the intended directory and transfer a harmless test file when write access is required. Verify that the account cannot browse unrelated subscription content. Remove the test file and record who owns the credential.
Resolve setup problems
For login success but no directory listing, investigate permissions and passive data connections. For an SFTP failure, confirm whether a separate SSH-enabled system account is required rather than assuming an FTP subaccount supports SFTP. Do not broaden the home directory or make all files writable simply to bypass a permissions error.