Skip to content

Knowledgebase

Creating restricted file-transfer access in Webuzo

control-panels, servers

Give a collaborator a dedicated file-transfer account limited to the directory they need. This is safer and easier to revoke than sharing the main Webuzo account or server administrator credential.

Check access and requirements

Confirm the required directory and whether the collaborator needs upload, download or deployment access. Back up content they can modify. Choose an encrypted transfer protocol supported by this server, and understand that an FTP account is not automatically an SSH or SFTP account.

01 Create restricted file-transfer access in Webuzo

  1. Open FTP > Add FTP Account in the end-user panel. Use a distinct username and unique strong password for this person or automation.
  2. Set Directory to the narrowest suitable path. Review the final path carefully so an upload-only task does not expose the whole account home.
  3. Set an appropriate quota where supported and create the account. Record its exact login name and the server hostname.
  4. Configure the client for the supported encrypted FTP connection, validating the server certificate. If you need SFTP instead, request or configure the separately authorized SSH-based access rather than assuming these FTP credentials will work.
  5. Upload a harmless test file, download it, and confirm that navigation outside the permitted scope is blocked as intended. Remove the test file afterward.
  6. Revoke the account when the work ends and rotate any shared deployment secret that was unnecessarily exposed.

Can I give every developer one shared FTP login?

Separate credentials make revocation and incident investigation clearer. Shared access makes it harder to identify which integration or person needs to be disabled when a credential is compromised.

Confirm the expected result

Confirm the collaborator can reach only the intended directory and that transferred files have suitable ownership and permissions. Test the affected website after a deployment. Check that certificate validation is enabled and that no account-wide credential was substituted.

Resolve setup problems

If login works but directory listing fails, investigate passive-mode networking and the server firewall configuration. If uploads fail, check quota, directory permissions and storage space. Do not solve either problem by granting world-writable permissions or exposing unrestricted administrative access.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support

Powered by WHMCompleteSolution