• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Plesk 9.3 Assigning a domain to a client

MikeyMacbeth

New Pleskian
Hi,

Currently I have all domains under the admin account (I'm using plesk 9.3 on Linux via webfusion)

I have a currently set up domain with emails addresses configured and the website up and running (it uses an existing mysql database) - my client is wanting control panel access and the ability to configure his own emails etc

Am I right in thinking that if I simply create him as a client with the relevant priveleges/settings and then assign the domain to the newly created client that all the email addresses, existing emails (he is accessing these via Horde webmail) and domain settings will transfer smoothly over with no interruption of service?

In short - are there any pitfalls to doing this or is it just a case of assigning him to the new client account? will the database that the website currently uses still be accessible?

Mike
 
Back
Top