---
title: "Track Remediation"
description: "This guide explains how to use the system to track and manage the remediation of identified issues, referred to as \"findings.\" Effective remediation tracking ensures that all issues are addressed p..."
last_updated: "2026-05-06T07:36:18.453172+00:00"
canonical_url: "https://www.doc0.dev/docs/49c89830-117b-4def-8edc-b5bcc50766e0/guide/section-3/track-remediation"
---

This guide explains how to use the system to track and manage the remediation of identified issues, referred to as "findings." Effective remediation tracking ensures that all issues are addressed promptly, responsibilities are clear, and progress is transparent.

The system provides tools to manage the lifecycle of findings, from their initial identification to their final resolution. This includes updating their status, assigning them to team members, adding comments for collaboration, and reviewing a complete history of changes. You'll also receive notifications about important updates to help you stay informed.

### Key Concepts

*   **Findings**: These are identified issues, vulnerabilities, or non-compliance points that require attention and resolution. Each finding has a lifecycle that you can track.
*   **Finding Status**: This indicates the current stage of a finding's remediation process. Common statuses include:
    *   **Open**: The finding has been identified and needs to be addressed.
    *   **In Progress**: Work has begun to remediate the finding.
    *   **Resolved**: The finding has been addressed, but may still require verification.
    *   **Closed**: The finding has been fully remediated and verified.
*   **Comments**: These allow you to communicate with team members directly within the context of a finding or related task. You can ask questions, provide updates, or share relevant information.
*   **Tasks**: While not explicitly detailed here, findings are often associated with tasks that represent the specific actions needed for remediation. Changes to these tasks (like assignee or status) can trigger notifications.

### Tracking Remediation Progress

The primary way to track remediation is by updating the status of findings and collaborating through comments.

<Steps>
<Step>
### View Findings
You can view all findings across your organization or filter them by specific criteria.

1.  Navigate to the "Findings" section in the application.
2.  To see all findings, select the "Organization" view.
3.  To narrow down the list, you can filter by:
    *   **Status**: For example, view only "Open" or "In Progress" findings.
    *   **Associated Task**: If a finding is linked to a specific task.
    *   **Evidence Submission**: If a finding is related to a particular evidence submission.
    *   **Evidence Form Type**: To see findings from specific types of evidence forms (e.g., "access-request").

</Step>
<Step>
### Update a Finding's Status
Changing a finding's status is crucial for reflecting its current remediation stage.

1.  Locate the specific finding you wish to update.
2.  Open the finding's details page.
3.  Look for the status field, usually presented as a dropdown or button.
4.  Select the appropriate new status (e.g., "In Progress," "Resolved").
5.  Save your changes.

<Callout variant="warning" title="Permissions for Status Changes">
Changing a finding's status may be restricted based on your user role. For example, only Auditors or Platform Admins might be able to mark a finding as "Closed." If you cannot change a status, contact an administrator.
</Callout>
</Step>
<Step>
### Add Comments to a Finding
Comments facilitate communication and provide context for remediation efforts.

1.  Navigate to the finding or task you want to comment on.
2.  Locate the comments section, typically at the bottom of the details page.
3.  Type your message in the comment box.
4.  You can mention other users by typing `@` followed by their name, which will send them a notification.
5.  Click "Post Comment" or similar to add your comment.

<Callout variant="info">
You can also update or delete your own comments if needed.
</Callout>
</Step>
<Step>
### Review Finding History
The history log provides an audit trail of all changes made to a finding.

1.  Open the details page for the finding you are interested in.
2.  Look for a section labeled "Activity," "History," or "Audit Log."
3.  This section will display a chronological list of events, such as status changes, assignee changes, and comments, along with who made the change and when.

</Step>
</Steps>

### Notifications

To keep you informed about remediation progress and collaboration, the system sends email notifications for key events:

*   **Task Status Changed**: You will receive an email if the status of a task you are involved with changes (e.g., from "Open" to "In Progress").
*   **Task Assignee Changed**: If a task you are assigned to, or a task you created, is reassigned to someone else, you will be notified.
*   **Comment Mention**: If another user mentions you in a comment on a finding or task, you will receive an email notification with the comment's content and a link to view it.

<Callout variant="info">
You can manage your email notification preferences to control which types of alerts you receive. Look for a link to "Manage your email preferences" in the footer of any notification email.
</Callout>

### User Roles and Permissions

Certain actions related to findings are restricted to specific user roles to maintain control and accountability:

<Accordions>
<Accordion title="Who can create, update, or delete findings?">
Only users with `Auditor`, `Admin`, or `Owner` roles, or Platform Admins, are authorized to create, update, or delete findings. Regular members can view findings and add comments, but cannot modify the finding's core details or status.
</Accordion>
<Accordion title="Who can change finding status?">
While many users might be able to update a finding's status to "In Progress" or "Resolved," specific transitions, such as marking a finding as "Closed," might be reserved for `Auditor`, `Admin`, or `Owner` roles.
</Accordion>
</Accordions>

## Sitemap

See the full [sitemap](https://www.doc0.dev/docs/49c89830-117b-4def-8edc-b5bcc50766e0/llms.txt) for all pages in this wiki.
