Account structure changes
The below covers specific changes between the legacy and new platform around account structure and how to resolve.
Multiple users moving to sub-accounts
If you have multiple users on your account there is a chance your account structure will have changed slightly with the new platform. All users will have their own sub-account so that they can maintain their personal inbox, contacts, products etc if these were being used. For the main admin user on the legacy account they will receive an additional username login for the super-account, this manages all the sub-accounts and has the main account settings ie. shop products, credit & billing and sub-account management. The new username login will be sent on email to the main admin user of the legacy account and the password will be the same as their previous account.
More information on account and user setup
Shared groups (including shortcodes):
In the legacy platform there was the ability to share a contact group (that could be connected to a shortcode keyword) with other users on the account. The new platform does not have the concept of sharing a group with other accounts at this time. In the new platform the shared groups will reside with the original creator. Even if setup with a shortcode keyword, the contact group can only be used on the original ‘creator’ account and not shared with multiple accounts.
To manage this change there are several possibilities; if it is just the contact group list required you could download/ re-upload onto all required accounts. Alternatively, the account which the contact group and shortcode keyword now reside with, could set up an additional user. But please note, sending would still need to be completed within the original creator account and the newly created user would have access to all features and information of the original ‘creator’ account.
For some customers the contacts & groups of these shared groups have been copied during migration to the new platform, onto any user’s sub-account who had access to them in the legacy platform. This will allow all users to see the same contacts and groups they had before and continue sending, making the workflow easier. But please note, these contacts & groups are a copy of the original shared groups, not the same group, so any changes and edits made to the original group will not be passed on to the sub-accounts who have a copy. There is future capability for the new platform that will allow this but won’t be available on migration. For any further questions please contact our support team.
VMNs/ Shortcode keywords:
These will reside in the sub-account of the user that purchased the product originally, as these are personal to your user account. If another users needs to access them you can manage this by adding the user on the sub-account with the product on (But please note: the user will have access to all features and information on that account including sending, sent data, and contacts).
In the legacy platform the blacklist was only on one account which was shared across all users. On the new platform we have moved multiple users to sub-accounts to protect their personal contacts and messages, however the blacklist resides at the super-account level only, and at at this time cannot be shared with multiple accounts. To manage this change the static blacklist can be downloaded from the super-account and re-uploaded to the sub-accounts as required.
Within the legacy platform API settings were managed in the Clockwork interface. These include multiple API keys and IP filtering. Within the new platform we have brought all the features together into one account to make it simpler to manage. This means that any users who were on the Clockwork accounts will now have access to the super-account on the new platform so they can manage the API settings (under Account settings).
For a pre-pay customer on the legacy site credit would have been shown on all user accounts, and was shared across all users on the account. This principle is the same on the new platform, however, if a user is reviewing this at a sub-account level they will see a “0” balance as they do not have any of their own balance, but are using the super-account credit balance instead. The user on the sub-account can continue to send messages using the super-account credit, but they cannot see how much credit is available or set a low credit alert (which can be done by users on the super-account; view credit by editor level, set low credit reminder at admin level).