• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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