Configure content remediation

As a Sensitive Content Admin, you can configure how content remediation behaves for your organization: when it appears on a board, how much manual reclassification reviewers are allowed to do, and whether reviewers can report a detected match as a false positive.

For an explanation of what content remediation is and why it exists, see Content remediation overview.

Prerequisites

• You must have the Sensitive Content Admin role. To request the role, contact your Company Admin. Admins can also create a custom role with the Content Remediation privilege and assign it to other users. Those users can then configure content remediation without needing the full Sensitive Content Admin role.
• You must define auto-classification before content remediation can activate. See Define Auto-classification.
• If you plan to set the trigger to Automatic classification and Guardrails, you must define at least one guardrail on a classification level first. See Define guardrails.

Configure content remediation

1. Go to your Miro settings.
2. On the left pane, under Enterprise Guard, click Content remediation.
3. Click Edit.

Step 1: Define

1. Under Conditions, review Who can review. This is currently fixed to Board owners, co-owners and editors, the people who can open content remediation, review findings, and take action.
2. Set Trigger to choose when content remediation appears on a board:
   • Automatic classification means content remediation appears whenever a detected sensitivity label triggers auto-classification on the board, regardless of the board's current classification level. For example, a detected label might auto-classify a board as Confidential. If someone later changes the board to Internal, content remediation still appears, because the check depends on the detected label rather than the board's current state.
   • Automatic classification and Guardrails means content remediation appears only when a detected sensitivity label triggers auto-classification. It also requires that at least one guardrail is configured on the resulting classification level. Choose this option if you don't want to show content remediation on boards where nothing is actually being restricted.
   • For detailed examples of when content remediation triggers, see When content remediation triggers in Content remediation overview .
3. Under Review settings, set Manual reclassification:
   • Allow manual reclassification lets reviewers change a board's classification level up or down with no restriction. Content remediation is informational only and never blocks a change.
   • Stricter only restricts how reviewers can change the classification. They can only move it to a level that is equal to or higher than the minimum level determined by the auto-classification configuration, not the board's current classification level.
   • For examples of how the minimum reclassification level is determined, see Reclassifying a board with content remediation active in Content remediation overview.
4. Under Actions, turn the Report false match toggle on or off:
   • On means reviewers can report a detected match to an Admin as a false positive.
   • Off means reviewers can view detected matches, but the option to report a false positive is hidden.
5. Click Next.

Step 2: Review

1. Review the Conditions, Review settings, and Actions summary.
2. Click Publish configuration.

Your changes apply only to boards where content remediation is active, and take effect immediately after publishing.

Edit or deactivate content remediation

After you publish a configuration, the Content remediation page shows your current settings.

• Edit opens the Define step so you can change any setting, then walk through Review again.
• Deactivate content remediation turns the feature off for your organization. Auto-classification and guardrails keep running independently; reviewers just no longer see the content remediation view on boards.