Sub-Accounts - Revision history

SarahK at 18:01, 5 May 2022

2022-05-05T18:01:21Z

PeterM at 14:26, 17 November 2020

2020-11-17T14:26:03Z

SarahK: /* What are Sub-Accounts? */

2020-08-04T13:10:29Z

‎What are Sub-Accounts?

SarahK: /* Creating/Modifying a Sub-Account */

2020-05-05T21:26:30Z

‎Creating/Modifying a Sub-Account

SarahK at 17:37, 5 May 2020

2020-05-05T17:37:13Z

John: /* How do Support Tickets work with them? */

2018-09-11T10:00:05Z

‎How do Support Tickets work with them?

Nathan: /* Creating/Modifying a Sub-Account */

2016-09-13T13:17:17Z

‎Creating/Modifying a Sub-Account

Nathan: /* Creating/Modifying a Sub-Account */

2016-09-13T13:15:51Z

‎Creating/Modifying a Sub-Account

John: /* Creating/Modifying a Sub-Account */

2016-02-01T14:59:33Z

‎Creating/Modifying a Sub-Account

John: /* Creating/Modifying a Sub-Account */

2010-05-15T11:50:04Z

‎Creating/Modifying a Sub-Account

@@ Line 4: / Line 4: @@
 </div>
-==What are Sub-Accounts?==
+Sub-Accounts are an extension of the '''[[Clients:Contacts Tab|Contacts]]''' feature. They allow clients to create sub-users under their main accounts, which then allow that contact to log in and perform various actions that the main account holder has permitted.
-Sub-Accounts are an extension of the Contacts feature. They allow clients to create sub-users under their main accounts, which then allow that contact to log in and perform various actions that the main account holder has permitted.
+The primary account is the master account owner, and any users they create under their account are sub-accounts.
 ==Why would a client use them?==
-Each section of the client area has its own permission setting. The master account holder (and any sub-accounts with the right permissions) can fine-tune the access rights to create different logins for different purposes.
+Each section of the Client Area has its own permission setting. The master account holder (and any sub-accounts with the right permissions) can fine-tune the access rights to create different logins for different purposes.
 For example:
@@ Line 27: / Line 25: @@
 One contact user will not receive email updates about the tickets that another contact submits, but they can still view all the tickets belonging to the master account holder when logging in.
-If the master account holder submits a ticket, all Support contacts will receive a copy of email notifications pertaining to the ticket.
+If the master account holder submits a ticket, all support contacts will receive a copy of email notifications pertaining to the ticket.
 ==Creating/Modifying a Sub-Account==
-To create a sub-account, begin by creating or locating an existing contacts record. You can do this in the client area by going to '''Client Area > My Details > Add New Contact''' or '''Manage Contacts''', or, on the admin side, by going to the '''Contacts''' tab under the client in question.
+To create a sub-account:
-*'''Change Password''' — All sub-accounts can access this page. It allows them to change their own login passwords.
+# Create a new contact or locate an existing contacts record. You can do this in the Client Area at '''Client Area > My Details''' or '''Manage Contacts''', or in the Admin Area in the '''[[Clients:Contacts Tab|Contacts]]''' tab in the client's profile.
-*'''View & Manage Contacts''' — This allows access to view and edit all contact users belonging to the master account.
+# Check the '''Sub-Account''' checkbox.
-*'''Manage Domain Settings''' — This allows sub-accounts to view and change, for example, nameservers, locking status, or WHOIS information.
+# Enter a password.
-*'''View & Pay Invoices''' — This allows sub-accounts to view and pay invoices and to access the following sections of the Client Area: [[Clients:Invoices_Tab|My Invoices]], [[Add_Funds|Add Funds]], [[Clients:Invoices_Tab|Mass Pay]], and [[Pay_Methods|Pay Methods]].
+# Check the various options for which you want to grant the sub-account permission to access. For example:[[File:Subpermissions.png|581px]]
-*'''Allow Single Signon''' — This allows the client to log in to a hosting account's control panel via Single Sign On (for example, logging in to cPanel).
+#*'''Change Password''' — All sub-accounts can access this page. It allows them to change their own login passwords.
 It is important to note that multiple contacts can have the same email address when for email notifications, but, if they are sub-accounts, the email address must be unique since it is part of the user's login.
@@ Line 49: / Line 47: @@
 When the sub-account user logs in, they see exactly the same client area that the master account owner would see. However, they can't view areas that they don't have permission to access.
-The screenshot below shows the error page that displays if a Sub-Account user tries to access an area that they don't have permission for. Rather than simply dead-ending them with an access denied error, it gives them an explanation of what areas they can access and what to do if they think this is incorrect.
+The screenshot below shows the error page that displays if a sub-account user tries to access an area that they don't have permission for. Rather than simply dead-ending them with an access denied error, it gives them an explanation of what areas they can access and what to do if they think this is incorrect.
 [[File:Subaccess-new.png]]
 [[Client_Management|<< Back to Client Management]]

@@ Line 49: / Line 49: @@
 When the sub-account user logs in, they see exactly the same client area that the master account owner would see. However, they can't view areas that they don't have permission to access.
-The screenshot below shows the error page that displays if a Sub-Account user tries to access an area that they don't have permission for. Rather than simply dead-ending them with an access denied error, it gives them an explanation of what areas they can access and what to do if they think this is incorrect. The welcome message at the top right of the screen is a small personalization that will show the sub-account user's own name, while the account information at the bottom right shows the information for their corresponding master account owner.
+The screenshot below shows the error page that displays if a Sub-Account user tries to access an area that they don't have permission for. Rather than simply dead-ending them with an access denied error, it gives them an explanation of what areas they can access and what to do if they think this is incorrect.
-[[File:Subaccess.png]]
+[[File:Subaccess-new.png]]
 [[Client_Management|<< Back to Client Management]]

← Older revision		Revision as of 13:10, 4 August 2020
Line 1:		Line 1:
		+	<div class="docs-alert-info">
		+	<span class="title">For WHMCS 7.10 and earlier</span><br />
		+	We removed the Sub-Accounts feature and associated functionality in WHMCS 8.0.
		+	</div>
		+
	==What are Sub-Accounts?==		==What are Sub-Accounts?==

@@ Line 35: / Line 35: @@
 *'''View & Manage Contacts''' — This allows access to view and edit all contact users belonging to the master account.
 *'''Manage Domain Settings''' — This allows sub-accounts to view and change, for example, nameservers, locking status, or WHOIS information.
-*'''View & Pay Invoices''' — This allows access to the change credit card details page of the client area.
+*'''View & Pay Invoices''' — This allows sub-accounts to view and pay invoices and to access the following sections of the Client Area: [[Clients:Invoices_Tab|My Invoices]], [[Add_Funds|Add Funds]], [[Clients:Invoices_Tab|Mass Pay]], and [[Pay_Methods|Pay Methods]].
 *'''Allow Single Signon''' — This allows the client to log in to a hosting account's control panel via Single Sign On (for example, logging in to cPanel).

@@ Line 1: / Line 1: @@
 ==What are Sub-Accounts?==
-An extension of the Contacts feature, Sub-Accounts allow clients to create sub-users under their main account, which then allows that contact to login, and carry out various actions that the main account holder has permitted them to.
+Sub-Accounts are an extension of the Contacts feature. They allow clients to create sub-users under their main accounts, which then allow that contact to log in and perform various actions that the main account holder has permitted.
-We call the primary login the master account owner, and any users they create under their account Sub-Accounts.
+The primary account is the master account owner, and any users they create under their account are Sub-Accounts.
 ==Why would a client use them?==
-Each section of the client area has it's own permission setting so the access rights can be fine tuned by the master account holder (and any sub-accounts given permissions to manage contacts) to create different logins for different purposes.
+Each section of the client area has its own permission setting. The master account holder (and any sub-accounts with the right permissions) can fine-tune the access rights to create different logins for different purposes.
-Just a couple of examples where this might be useful are:
+For example:
-*'''Billing Department''' - corporate users may have a dedicated billing department who should be given access to pay invoices and place new orders while the web/technical staff would only be given access to view current products & services and submit support requests, which was previously impossible
+*'''Billing Department''' — Corporate users may have a dedicated billing department that needs access to pay invoices and place new orders, while the web or technical staff would only need access to view current products and services and submit support requests.
-*'''Web Developers''' - a customer hosting with you may be employing a web developer to build and maintain their website so might want to give that developer access to create tickets and correspond on their behalf, without being able to access any billing information or change account details
+*'''Web Developers''' — One of your customers may be employing a web developer to build and maintain their website, so they might want to give that developer access to create tickets and correspond on their behalf without being able to access any billing information or change account details.
-As before there's also the email preferences for a contact/sub-account so they can be used for having invoice related emails sent to additional email addresses.
+You can use email preferences for contacts and sub-accounts so that the system sends invoice-related emails to additional email addresses.
 ==How do Support Tickets work with them?==
-If a sub-account user opens a support ticket, then they will be CC'd any replies relating to that ticket by email along with the master account holder. Contacts can also open tickets simply by emailing if piping is enabled, and the emails from them will be automatically collected and assigned to the master client account.
+If a sub-account user opens a support ticket, the system will CC them (and the master account holder) for any replies relating to that ticket. Contacts can also open tickets by email if you have enabled piping. The system automatically collects these emails and assigns them to the master client account.
-One contact user will not receive email updates about the tickets submitted by another contact, but they can still view all the tickets belonging to the master account holder when logging in.
+One contact user will not receive email updates about the tickets that another contact submits, but they can still view all the tickets belonging to the master account holder when logging in.
-If a ticket is submitted by the master account holder, all Support contacts will receive a copy of email notifications pertaining to the ticket.
+If the master account holder submits a ticket, all Support contacts will receive a copy of email notifications pertaining to the ticket.
 ==Creating/Modifying a Sub-Account==
-To create a sub-account, begin by creating or locating an existing contacts record. This can be done in the client area by going to '''Client Area > My Details > Add New Contact''' or '''Manage Contacts''' or on the admin side by going to the '''Contacts''' tab under the client in question.
+To create a sub-account, begin by creating or locating an existing contacts record. You can do this in the client area by going to '''Client Area > My Details > Add New Contact''' or '''Manage Contacts''', or, on the admin side, by going to the '''Contacts''' tab under the client in question.
-Then to convert the contact into a sub-account, and therefore allow the contact to login, just tick the '''Sub-Account''' checkbox. Next enter a password and then tick the various options that you want to grant the sub-account permission to access.  Below is a screenshot of the client area configuration screen for a sub-accounts permissions.
+Then, to convert the contact into a sub-account and allow the contact to log in, just check the '''Sub-Account''' checkbox. Next, enter a password. Check the various options for which you want to grant the sub-account permission to access.  Below is a screenshot of the client area configuration screen for a sub-accounts permissions.
 [[File:Subpermissions.png|581px]]
-The permissions are mostly self explanatory but some clarifications:
+*'''Change Password''' — All sub-accounts can access this page. It allows them to change their own login passwords.
-*'''Change Password''' - this page can be accessed by all sub-accounts and allows them to change their own login password
+It is important to note that multiple contacts can have the same email address when for email notifications, but, if they are sub-accounts, the email address must be unique since it is part of the user's login.
 ==What does the Sub-Account user see?==
-When the sub-account user logs in, they see exactly the same client area that the master account owner would see, albeit they can't view areas that they don't have permissions to access.
+When the sub-account user logs in, they see exactly the same client area that the master account owner would see. However, they can't view areas that they don't have permission to access.
-The screenshot below shows the error page which is shown if a Sub-Account user tries to access an area that they don't have permission for. Rather than simply dead-ending them with an access denied error it gives them an explanation of what areas they can access and what to do in the case they think this is incorrect. A small personalisation touch is the welcome message at the top right of the screen which will show the sub-account users own name, while the account info at the bottom right shows the master account info they are a member of.
+The screenshot below shows the error page that displays if a Sub-Account user tries to access an area that they don't have permission for. Rather than simply dead-ending them with an access denied error, it gives them an explanation of what areas they can access and what to do if they think this is incorrect. The welcome message at the top right of the screen is a small personalization that will show the sub-account user's own name, while the account information at the bottom right shows the information for their corresponding master account owner.
 [[File:Subaccess.png]]
 [[Client_Management|<< Back to Client Management]]

← Older revision		Revision as of 10:00, 11 September 2018
Line 21:		Line 21:

	One contact user will not receive email updates about the tickets submitted by another contact, but they can still view all the tickets belonging to the master account holder when logging in.		One contact user will not receive email updates about the tickets submitted by another contact, but they can still view all the tickets belonging to the master account holder when logging in.
		+
		+	If a ticket is submitted by the master account holder, all Support contacts will receive a copy of email notifications pertaining to the ticket.

	==Creating/Modifying a Sub-Account==		==Creating/Modifying a Sub-Account==

@@ Line 28: / Line 28: @@
 Then to convert the contact into a sub-account, and therefore allow the contact to login, just tick the '''Sub-Account''' checkbox. Next enter a password and then tick the various options that you want to grant the sub-account permission to access.  Below is a screenshot of the client area configuration screen for a sub-accounts permissions.
-[[File:Subpermissions.png]]
+[[File:Subpermissions.png|650px]]
 The permissions are mostly self explanatory but some clarifications:

@@ Line 32: / Line 32: @@
 The permissions are mostly self explanatory but some clarifications:
-*Change Password - this page can be accessed by all sub-accounts and allows them to change their own login password
+*'''Change Password''' - this page can be accessed by all sub-accounts and allows them to change their own login password
-*View & Manage Contacts - this allows access to view & edit all contact users belonging to the master account
+*'''View & Manage Contacts''' - this allows access to view & edit all contact users belonging to the master account
-*Manage Domain Settings - this refers to being able to view & change nameservers, locking status, WHOIS information, etc...
+*'''Manage Domain Settings''' - this refers to being able to view & change nameservers, locking status, WHOIS information, etc...
-*View & Pay Invoices - this includes allowing access to the change credit card details page of the client area
+*'''View & Pay Invoices''' - this includes allowing access to the change credit card details page of the client area
 It is important to note that multiple contacts can have the same email address when being used for email notifications only, but if activating them as a Sub-Account the email address must be unique since it will be used for the login.