Summary of best practices<\/a><\/li><\/ul><\/nav><\/div>\n\n\n\n
\n\n\n\nUnderstanding the Plesk hierarchy and vocabulary<\/h2>\n\n\n\n
First of all, here's how the elements are organized in Plesk :<\/p>\n\n\n\n
Customer \u2192 Subscription \u2192 Domain \/ Alias<\/strong><\/p>\n\n\n\nAll this under the supervision of a Service package<\/strong>, which defines the resources and rights associated with each subscription.<\/p>\n\n\n\n\n- Customer<\/strong> an account created in your reseller area for one of your customers.<\/li>\n\n\n\n
- Service package<\/strong> A template of resources and rights (disk space, PHP, etc.) that you apply to a subscription.<\/li>\n\n\n\n
- Subscription<\/strong> Hosting space (resources, disk quota, features). This is the central unit of Plesk.<\/li>\n\n\n\n
- Domain<\/strong> the main website linked to a subscription.<\/li>\n\n\n\n
- Alias<\/strong> an additional domain pointing to the same subscription (see dedicated section).<\/li>\n<\/ul>\n\n\n\n
\n\n\n\nOur customers<\/h2>\n\n\n\nWhat is a \u00abclient\u00bb in Plesk?<\/h3>\n\n\n\n
A customer is an account created in your reseller space, enabling one of your customers to connect to Plesk and access its own accommodation<\/strong>, without seeing yours.<\/p>\n\n\n\nIs creating a customer mandatory?<\/h3>\n\n\n\n
No.<\/strong> You can manage subscriptions without creating associated customers - in which case only you have access to them.<\/p>\n\n\n\nCreating a customer is useful if :<\/p>\n\n\n\n
\n- you wish to give your customer Plesk access<\/strong> so that it can access its data and manage its own hosting (FTP access, email addresses, WordPress Toolkit, DNS zone, external backups, etc.);<\/li>\n\n\n\n
- you wish to get better organized<\/strong> by directly observing who owns each subscription.<\/li>\n<\/ul>\n\n\n\n
NB: Certain rights granted to the client (such as access to PHP settings) are determined by the pack of services<\/strong> associated with it. See dedicated section.<\/em><\/p>\n\n\n\n