Create content incident folders to help you organize, monitor, and manage the incidents that content policy violations generate. You can have as many as 1,000 folders including the default Informational Incidents and Quarantine Incidents folders.
To create a content incident folder, you must have Full Administration rights or rights to modify policies.
In the Control Center, click Content > Settings > Content Incident Folders.
In the Content Incident folder name field, type a name for the content incident folder.
As a best practice, you should use a name that reflects the type of content that you intend to collect in that folder. For example, if you want to place the messages that violate a HIPPA policy in this folder, you might name the folder HIPPA.
Click the Content incident folder type drop-down list to select the type of folder you want to use.
Optionally, in the Optional archive tag field, type the text that you want to identify this folder with for archival purposes.
When you specify an archive action on an incident in this content incident folder, that text accompanies the incident.
If you specified an incident archive tag, in the Encoding drop-down list, choose the character encoding set to use for the tag text.
Check Enable message submission buttons within this folder to enable submission functionality.
This option only appears if you have enabled the customer-specific spam submission feature.
Click Edit to view or edit the incident notification template.
In the Notification recipient addresses field, type the email addresses of the content filtering officers who should be notified of incidents in this folder.
Separate multiple addresses with commas, semicolons, or spaces.
In the Administrator Notifications list, check the names of administrators whom you want to be notified of incidents in this folder. If you do not want to have notifications sent, leave this field blank.
You can specify administrators to notify of incidents in this folder when you add administrators or modify administrator settings.
Imported Document ID: HOWTO93050
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe