This article contains information on configuring Mimecast Content Overseers policies to assign users or groups to manage held messages without requiring admin access, including setup steps, usage scenarios, and policy customization options.
A Content Overseers policy assigns a group of users to act as overseers for messages in the on-hold queue. Content overseers don't require access to the Mimecast Administration Console. Instead, they can review, release, or reject messages by logging on to Mimecast Personal Portal, Mimecast Mobile, or Mimecast for Outlook. Once configured, they can oversee all messages held due to spam scanning, content examination, or attachment management policies.
This is useful in the following circumstances:
- A Personal Assistant requires access to a manager's (or a group of managers) hold queues, but who doesn't have access to their Mimecast accounts.
- For a Help Desk assisting in reviewing and releasing messages in the administration hold queue, but doesn't have access to the Administration Console.
- For a Compliance Team reviewing messages triggering a Content Examination policy configured to hold outbound mail that contains company-sensitive information.
Usage Considerations
Consider the following before creating a policy:
- We recommend using the Moderator Group options in spam scanning, content examination, or attachment management definitions, as these offer the same functionality as a Content Overseers policy.
- If multiple users are to be overseers, a group is required prior to configuring this policy. This group can be a local Mimecast group or a directory group.
- A Content Overseer policy takes effect on the next messages that match the content examination, spam scanning, or attachment management policy.
- If notifications are required for the overseers, these must be configured in the same policies mentioned above. If the policy is triggered, a content alert notification is sent to the members of the Content Overseers group. This notification can be amended using a notification set. See the Configuring Notification Sets page for full details.
Configuring a Content Overseers Policy
To configure a Content Overseers policy:
- Log in to the Mimecast Administration Console.
- Select the Policies | Gateway Policies menu item.
- Click on Content Overseers. A list of policies is displayed.
- Either select the:
-
-
- Policy to be changed.
- New Policy button to create a policy.
-
- Complete the Options section as required:
| Field / Option | Description |
|---|---|
| Policy Narrative | Provide a description for the Policy to allow you to easily identify it in the future. |
| Select Oversight Group | Use the Lookup button to select the group of users to act as overseers. |
- Complete the Emails From and Emails To sections as required:
| Field / Option | Description |
| Addresses Based On |
Specify the email address characteristics that the policy is based on. This option is only available in the "Emails From" section. The options are:
|
| Applies From / To |
Specify the sender characteristics the policy is based on. For multiple policies, you should apply them from the most to the least specific. The options are:
|
- Complete the Validity section as required:
| Field / Option | Description |
|---|---|
| Enable / Disable | Use this to enable (default) or disable a policy. If a date range has been specified, the policy will automatically be disabled when the end of the configured date range is reached. |
| Set Policy as Perpetual | If the policy's date range has no end date, this field displays Always On, meaning that the policy never expires. |
| Date Range | Use this field to specify a start and/or end date for the policy. If the Eternal option is selected, no date is required. |
| Policy Override | This overrides the default order in which policies are applied. If there are multiple applicable policies, this policy is applied first unless more specific policies of the same type are configured with an override. |
| Bi-Directional | If selected, the policy is applied when the policy's recipient is the sender, and the sender is the recipient. |
| Source IP Ranges (n.n.n.n/x) | Enter any required Source IP Ranges for the policy. These only apply if the source IP address used to transmit the message data falls inside or matches the range(s) configured. IP ranges should be entered in CIDR notation. |
- Click on the Save and Exit button.
Comments
Please sign in to leave a comment.