Advanced / Federated Account Administration: Account Structures

Document created by user.oxriBaJeN4 Employee on Sep 11, 2015Last modified by user.oxriBaJeN4 Employee on Oct 31, 2017
Version 5Show Document
  • View in full screen mode

Advanced Account Administration structureAccount hierarchy can only be applied in one jurisdictional region. Cross regional account hierarchies (accounts on multiple Mimecast grids) are currently not supported.

Advanced and federated account administration are designed in a hierarchy, that links the different account types together.

 

Accounts can be linked to each other to support an account hierarchy that provides segregated storage and / or security configuration features. Both advanced and federated account administration optionally offer:

 

Account Types

 

The various account types available with advanced / federated account administration are described below:

 

Account Type
Advanced Account Administration
Federated Account Administration
Master Account
  • Used for hierarchy management. Administrators on the master account can:
    • Register domain names, and allocate them to the nested mail processing accounts.
    • Retrieve user addresses via the mail processing account's directory connectors, or via a manual import.
    • Import users directly into the nested accounts, and migrate users between them.
    • Import administrators for selected roles into a nested mail processing account, but itself by default has only one administrator role.
  • Has a read only view of the authorized outbound IP addresses, internal domains, directory and journal connectors of the nested mail processing accounts.
  • Used for Hierarchy Management only.
  • By default has only one administrator role.
  • Has a read only view of the authorized outbound IP addresses and internal domains within the setup.
Group Account
  • Used to group nested mail processing accounts together.
  • Have no administrative roles available.
  • Hold a read only view of the authorized outbound IP addresses, internal domains, directory and journal connectors of the mail processing accounts nested underneath them.
  • Group nested mail processing accounts together.
  • Have no administrative roles available on group accounts.
  • Hold a read only view of the authorized outbound IP addresses and internal domains of the accounts nested underneath them.
Mail Processing Account
  • Process email.
  • Cannot add new internal domains. This is handled by the Master account.
  • Imported user addresses are automatically copied to the master account.
  • Importing addresses from other mail processing accounts isn't allowed. This is handled by the Master account.
  • User addresses cannot be imported into groups, and aren't automatically added to the internal domains based on outbound email flow.
  • Manual directory synchronization on the mail processing account triggers a manual synchronization on the master account.
  • Directory connectors, journal connectors, and authorized outbound IP addresses, are automatically copied to the master account when they're created.
  • Process email.
  • Identical to regular Mimecast accounts.

 

Managing Account Hierarchy

 

To manage your account hierarchy:

  1. Log on to the Administration Console of the master account.
  2. Click on the Administration toolbar menu item.
  3. Click on the Account | Hierarchy menu item. The Account management dialog is displayed.

    AAA_Account.png
  4. Navigate to, and click on, the Folder for the required nested account in the hierarchy. The group's nested mail processing accounts are displayed.
  5. From here you can:
    • Click on the View Details button to view that account's account settings.
    • Click on the View button to filter the list of accounts by either "Unlinked" or "Linked" accounts.
    • Click on the Consolidated View button for a full list of the group and mail processing accounts linked to the master account.
    • Right click an account in the hierarchy to change it's parent account (i.e. move it to another location in the hierarchy).

Attachments

    Outcomes