# Automated Actions

When a content scanning job is completed, Protege AI can automatically create remediation tickets in your task management system based on risk thresholds. This streamlines the process of addressing compliance issues found during web content monitoring.

## Overview

Automated actions for content scanning eliminate the manual step of creating tickets for policy violations. When a scan identifies issues that exceed your defined risk thresholds, change request tickets are automatically created with detailed information about the violations.

## How It Works

1. **Scan Completion**: A scheduled or one-time content scanning job finishes
2. **Risk Evaluation**: The entire report is evaluated against your configured risk thresholds
3. **Threshold Check**: If the aggregate risk score exceeds any defined threshold, an action is triggered
4. **Ticket Creation**: A change request ticket is automatically created in your task management system
5. **Details Included**: The ticket contains links to the scan report, specific violations, and affected pages

## Key Features

### Customizable Task Manager Integration

You can specify which project in your task management system should receive the change request tickets, ensuring seamless integration with your existing workflow.

### Individual Risk Thresholds

Each scanning job can have its own unique risk thresholds, allowing for tailored risk assessment based on:

* Content type (proprietary vs. third-party)
* Brand sensitivity
* Platform (social media vs. website)
* Compliance requirements

### Aggregate Risk Scoring

Actions are triggered based on the combined risk across all scanned pages, not individual violations. This prevents ticket overload while ensuring significant issues are escalated.

## Configuration

### Setting Up Automated Actions for Scanner Jobs

1. Navigate to **Content Scanner** in the dashboard
2. Create a new job or edit an existing scheduled job
3. Go to the **Actions** tab
4. Select a project to create tickets in from your connected task manager
5. Configure risk levels and occurrence counts:
   * **High Risk**: Number of high-risk violations that trigger action
   * **Medium Risk**: Number of medium-risk violations that trigger action
   * **Low Risk**: Number of low-risk violations that trigger action
6. Press **Proceed** to save your configuration

### Threshold Examples

**Conservative (High Sensitivity):**

* Create ticket if: ≥1 High risk, ≥3 Medium risk, ≥10 Low risk

**Moderate:**

* Create ticket if: ≥2 High risk, ≥5 Medium risk, ≥20 Low risk

**Lenient:**

* Create ticket if: ≥3 High risk, ≥10 Medium risk, ≥50 Low risk

## Ticket Contents

Automatically created tickets include:

* **Scan Report Link**: Direct link to the full Protege scan report
* **Summary**: Overview of violations found
* **Risk Breakdown**: Count of High, Medium, and Low risk issues
* **Affected Pages**: List of URLs with violations
* **Policy Types**: Categories of policies violated
* **Timestamps**: When the scan was completed
* **Brand Information**: Which brand(s) were affected

## Supported Task Managers

Automated actions for content scanning work with:

* Asana
* Jira
* Smartsheets
* Wrike

## Best Practices

* **Job-Specific Thresholds**: Use stricter thresholds for high-visibility content (homepage, landing pages)
* **Platform Considerations**: Social media may require more lenient thresholds due to user-generated content
* **Regular Adjustment**: Review and adjust thresholds based on your team's capacity and priorities
* **Brand Differentiation**: Apply different thresholds for different brands based on risk tolerance
* **Test First**: Run initial scans without actions enabled to calibrate appropriate thresholds

## Action History

Track all automated ticket creation:

1. Go to **Settings** → **Action History**
2. Filter by "Content Scanner" actions
3. Review which scans triggered automatic ticket creation
4. Analyze patterns to optimize thresholds

## Managing Created Tickets

Tickets created by automated actions can be:

* Assigned to specific team members
* Prioritized based on risk levels
* Tracked through your normal workflow
* Closed when issues are remediated
* Referenced for compliance audits

## Disabling Actions

To disable automated actions for a specific scanner job:

1. Edit the scanner job
2. Navigate to the **Actions** tab
3. Remove the project selection or adjust thresholds to prevent triggering
4. Save your changes

## Integration Notes

* Actions respect your task manager's project permissions
* Tickets are created under the Protege integration user
* Custom fields in your task manager can be populated (contact support)
* Ticket templates can be customized for your organization

For questions about configuring automated actions for content scanning, contact <founders@tryprotege.com>.