Sub-Accounts Print

  • Customer Backroom, Sub-Accounts
  • 4

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.

We will refer to the primary account login as the Master account owner, and any users they create under their account as Sub-Accounts.

Why would a client use them?

Each section of the AlpineWeb Customer Backroom 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.

Just a couple of examples where this might be useful are:

  • Billing Department: Customers may have a dedicated billing department or a bookkeeper who they would like to 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.

  • Web Developers: Customers may be employing a web developer to build and maintain their website and may 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.

There are also email preferences for a contact/sub-account which can be used for having invoice related emails sent 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 sending an email, and the emails from them will be automatically collected and assigned 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.

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 AlpineWeb Customer Backroom by going to:

Once logged in, navigate to:

Client Area > My Details > Add New Contact or Manage Contacts

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:

 Sub Accounts

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.

  • 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...

  • 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.

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, but they cannot view areas that they do not have permissions to access.

An error page will be displayed if a Sub-Account user tries to access an area that they don't have permission for. An explanation of what areas they can access and what to do in the case they think this is incorrect. A welcome message at the top right of the screen 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.


Was this answer helpful?

« Back