Any incident flagged by a policy that has not been changed to another status manually or by a policy response action. While an incident remains in this status, no additional incidents will raise for the offending file or app against this policy.
This status is primarily used by Cloudlock Admins to distinguish which incidents are under review but not completely addressed. This can be changed manually or as a Response Action. While an incident remains in this status, no additional incidents will raise for the offending file or app against this policy.
This status indicates that the violating offense that caused the incident to raise has been addressed and the file is no longer considered to be in violation. A Response Action Workflow that includes notifications, access revocation, etc. often ends with the incident status being updated to Resolved. As soon as an incident is Resolved, the file is eligible to be rescanned through the policy engine and will trigger a new incident if it violates the policy again in the future.
This status indicates that the violation has been reviewed by a Cloudlock Admin and not considered a true offense. This status essentially grants the offending document a "free-pass" against this policy from here on out. This file will never raise another incident against this policy again.
Example: A policy for Inappropriate Language raises an incident on a student's document. If the offending text is a quote from a novel containing expletives, the admin may be inclined to Dismiss the incident. This shows the incident has been reviewed, and deemed harmless - as a result, this file will never raise another incident against this policy. However, had the offending text been in a bullying manner, the file owner or teacher would most likely be contacted directly. Once the issue had been addressed, the incident could then be Resolved. This enables the file to raise a new incident should similar language appear in the document again.
Updated 10 months ago