Skip to content
Windows Hosting

How to Manage Plesk Users and Permissions Safely

In this article10 sections

A Plesk server often has more than one person working on it: a developer who deploys the site, a marketing person who edits pages, a bookkeeper who reads the statistics, and a freelancer who needs access for one project. Sharing the main administrator login gives each of them more power than they need, and it leaves no record of who did what. Plesk lets you create separate users, give each one access to the websites they work on, and remove that access when the work ends. This guide shows how to set that up, which permissions to give, and how to review them.

Siteharbour’s Windows hosting runs Plesk, so the steps below apply to any Plesk server you manage. Give each person the least access that lets them do their job.

Know the two levels of access

Plesk separates access to the server and access to a subscription, which is the set of websites for one customer or project. A server administrator controls the whole machine, and should be as few people as possible. A subscription user controls only the websites in that subscription. Most people who work on a site need the second level, not the first.

Step 1: Create a user for the subscription

In Plesk, open the subscription for the website, and select the option to add a user. Enter a name, a work email address, and a strong password from a password manager. Give the user a role that matches the work. A role with fewer rights is the safer default, and you can raise it later if the person needs more.

Expected: the user appears in the subscription’s user list with the role you chose. The user can sign in and see only the websites in that subscription.

Step 2: Choose the right role

Plesk roles bundle permissions, so you choose one role rather than many switches. As a guide:

  • Read-only or statistics access for someone who needs to see reports and not change anything.
  • Content access for someone who edits pages, such as a marketing person, without access to the files or the databases.
  • Development access for a developer who deploys code and manages databases for the site, but not the server.

Check the permissions the role grants in the role’s details before you assign it. Plesk shows the list, and the list changes between versions, so read it rather than assume.

Step 3: Set separate FTP and SFTP access

Each person who uploads files should have their own FTP or SFTP account, not a shared one. Under the website’s FTP settings, create an account for the user, and point it at the website’s folder. A separate account lets you remove one person’s access without changing the password for everyone else. Use SFTP rather than plain FTP, because plain FTP sends the password unencrypted.

sftp -P 22 [email protected]

Expected: a prompt that asks for the user’s password, then a connection to the website’s folder. If the connection fails, check the port and that the account is set to the right folder.

Step 4: Limit access to the folders each person needs

A developer needs the code folder. A content editor needs the media folder and nothing else. Keep the folders separate, so an upload by one person cannot overwrite the work of another. Where the platform allows it, point each FTP account at the folder it needs, rather than the whole website.

Step 5: Remove access when the work ends

When a freelancer finishes a project, disable their user account in Plesk. Disabling is safer than deleting, because the account’s history stays in place, and you can turn it back on if the work resumes. Remove their FTP and SFTP accounts at the same time. Check that the password they had no longer works, by trying to sign in from a test session.

Step 6: Review the list every quarter

Once a quarter, open the user list for each subscription and check three things: that every user is still working on the site, that no one has more access than their work needs, and that no account is shared by two people. Write the date of the review in a note, so the next review has a reference. An unknown user in the list is a sign of an intrusion, so treat it as an incident and reset the server administrator’s password.

Step 7: Keep the administrator login for the server

The server administrator account should belong to one or two people, with a strong password and two-factor sign-in where Plesk allows it. Give everyone else a subscription user, so a mistake by a content editor cannot change the server’s settings. Keep the administrator’s password in a password manager, not in a shared document.

Common mistakes

  • Sharing one login. You cannot tell who changed what, and removing one person means changing the password for everyone.
  • Giving everyone the administrator role. A single mistake can affect the whole server.
  • Using plain FTP. The password crosses the network without encryption.
  • Deleting users instead of disabling them. You lose the history you may need.
  • Never reviewing the list. Old accounts stay active long after the work has ended.

Frequently asked questions

Can a subscription user see other customers’ websites?

No. A subscription user sees only the websites in their own subscription.

How do I see who changed a file?

Plesk’s logs record the account used for each change, and the FTP and SFTP logs show uploads. Keep the logs for a set period, so you can check an incident.

Should a developer have server access?

Only if the job requires it, such as managing the server’s configuration. Most development work fits a subscription role.

What if a user forgets their password?

Reset it from the user’s settings in Plesk, and send the new password through a channel you trust, not in plain email.

On a Plesk server, give each person their own user, choose the role that matches their work, and give each one their own FTP or SFTP account. Remove access by disabling the user when the work ends, and review the list every quarter. Keep the server administrator login to one or two people. For the security of the sites those users work on, read how to create a website and install SSL in Plesk.

Share this guide