Account owners can create sub-accounts, which are basically subsidiaries of the parent account in a parent-child hierarchy. Each sub-account can have its own Admin and User set, without having visibility of other sub-account activity, while any administrator of the parent account will have visibility of all sub-account activity.
An example of this might be a sales business with a structure divided into regions, with each region having a manager and a number of team members reporting to them. In this example, each region would be a sub-account (with the regional manager as the admin), and their team members would be users on that sub-account. The business owner would be the admin on the parent account:
To create a new sub-account or for any assistance, you can email email@example.com with your request.
Important things to remember:
- Consider a simple naming convention for your sub account so their ‘purpose’ is clear to others e.g. Business Auckland, Business Afterhours, Business Waikato, etc.
- The purpose of the parent account is to allow Admin visibility of sub accounts. No messages need be sent to and from the parent account but of course they can be.
- An administrative user on the Parent account may not necessarily have access to make changes to all sub-accounts. However, while they are logged into the Parent, they will still be able to 'see' these accounts, and moreover, be able to add themselves to them.
- It is recommended that all logins, whether Admin or User are personalised, otherwise anyone with access to a generic email address would be able to login and/or perform a password recovery function to gain access. It is generally not secure practice to 'share' logins.
- Contact Groups that are maintained at the Parent Account level can be shared to any/all sub accounts under that Parent. Updates to these lists on the Parent also flow down to the sub-accounts they are shared with. Access to contact Groups can also be revoked at any time by an Administrator.
- It is good practice to have Contact Group names follow a standard that is obvious to others i.e. Business unit / Territory / Workgroup
- Templates that are maintained at the Parent Account level ARE shared to all sub accounts under that Parent.
- Email to SMS and allowing Domain name sending. The ability to send messages from any email client e.g. MS Outlook, will apply to all email users once the domain name has been added to an account. All messages from this domain will then be consolidated to this account. Allowing for reporting on email to SMS use from this account.
Caution should be exercised when setting an entire domain with E2S access. Considerations are that you should ’own’ the domain you are sending from/adding (i.e. no ‘public’ domains such as gmail.com, or outlook.com). The domain whitelisting can only apply to one account. For example you cannot add ‘*@yourdomain.co.nz’ on an account if it is already whitelisted on another.