The Administration Console

Document created by user.oxriBaJeN4 Employee on Jun 1, 2016Last modified by user.oxriBaJeN4 Employee on Mar 27, 2017
Version 12Show Document
  • View in full screen mode

The Administration Console allows administrators to configure and monitor their Mimecast Accounts. The tasks they can perform include:

  • Managing user accounts and role based permissions.
  • Creating or amending policies.
  • Reviewing the logs to track user activity (e.g. to see who has amended a policy, logged onto Mimecast, or performed an archive search).
  • Troubleshooting email delivery to determine why an email has been delayed or failed delivery.

Your Mimecast subscription, together with a user's administrator role, determines what tasks you can perform.

When your Mimecast account is created, various default administrator accounts are created with it. Each account has different permissions, controlled by roles. These roles control the menus and options a user account has access to, so allowing granular control of permissions and enhanced security. You can change these roles, and the permissions each user has, at any time.

 

Using the Mimecast Administration Console

 

During the Mimecast implementation process, administrator accounts are created. Each account is assigned to a specific role, which provides access to various menus and options. Using roles, administrators can have different permissions and access to varying tasks. This allows granular control of permissions and enhanced security. See the Understanding Administrator Roles page for further details.

 

To access the Administration Console, the administrator must log in. Once logged in, the dashboard is displayed. This displays views of queue levels, email traffic flow, service notifications, and product news all in one central location. See the Logging in to the Administration Console page for further details.

For security reasons, administrators are automatically logged off after a period of inactivity. Any interaction with an expired session requires them to log back in to continue.

See Also...

 

4 people found this helpful

Attachments

    Outcomes