• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Restricting/sandboxing Child site administration/access

RobCSB

New Pleskian
I am a new Plesk ONYX customer.

I have a subsciption configured and functional...let's call it SAMPLE.COM. It's up and running no problems.

I have created a child domain, CHILD.SAMPLE.COM. That site is up and running.

I just noticed that the user account specified for FTP/SSH access for SAMPLE.COM can manage CHILD.SAMPLE.COM.

How can I create a limitation so that I can have a different user who can only manage CHILD.SAMPLE.COM. (By Manage, I really mean FTP/SSH access and limited access to that site via the PLESK Console.

I do not want to have a situation where child sites administrative access accounts can have access to all other child sites. They need to be sandboxed so that CHILDUser can only manage CHILD.SAMPLE.COM, not the parent (SAMPLE.COM nor CHILD2.SAMPLE.COM, etc.)

Thank you.
 
Back
Top