Skip to main content

Sub accounts

  • Updated

This article explains what sub accounts are, how you can enable, create and configure them, and what the benefits are to using them.

  • Sub accounts are subsidiaries of parent accounts, admins of parent accounts are able to create them and add users to them.
  • Each sub account can have its own admin and user set, without having visibility of other sub account activity.
  • Admins of the parent account have visibility of all sub account activity. For more information about user hierarchies you can review this article User Roles.

Benefits of using sub accounts

  • Team members needing to access to the platform can do so without necessarily having access to their colleagues/ other departments accounts. You can however choose to share contact lists and templates between sub accounts so that they don't need to be re-created.  
  • If a user leaves the organisation, they can simply be removed from the account or sub account, without impacting any data or other users.
  • If you want to use your account to send messages relating to marketing, sales, finance and rostering, then you could create a sub account for each department.
  • You can have separate inboxes and reporting - making it a lot easier to manage campaigns and engagement.

Create / remove a sub account

In order to create or delete/ remove a sub-account, please email mobiledirect@spark.co.nz (enterprise/ corporate) or webservices@spark.co.nz (hub customers) with your request.

Once created, to navigate between your sub accounts you can use the account switcher.

Sub accounts page

From the sub accounts page, you can:

  • Review a list of all sub accounts
  • See how many SMS each sub account has sent within the last month
  • See how many users there are of each sub account
  • Login to all sub accounts
Sub accounts page screenshot

Users and Sub accounts

A user is a profile with access to login to the portal, be it to the parent account or a sub account. A user can be invited to one or more accounts by an account administrator, please see this article for a breakdown of the permissions held by each user type. Below is an example of a basic account structure, with four sub-accounts below the parent account, each having its own set of users:

Related articles