Filter and view unread requests

Understanding unread request types

Unread requests are organized into three categories, each serving a different purpose:

• Unread new requests: A new request is a request that you haven't entered yet. These are fresh inquiries from data subjects that require an initial review. Once you enter a new request (by clicking into it), it automatically moves out of this category—even if you don't take any action on it.

• Unread new responses: A new response indicates that an data subject has replied to an existing request, and you haven't read their latest message yet. This helps you quickly identify ongoing conversations that need your attention. Once you enter the request with the new response, it is no longer categorized as having a new response.

• All unread: The all unread category is an umbrella view that includes new requests, new responses, and any requests you've manually marked as unread. This gives you the broadest view of everything in your queue that hasn't been fully addressed.

Filtering unread requests

You can filter your requests using the "For review" dropdown, which now includes specific options:

• Required attention - Requests that have been flagged with a flag icon as needing immediate attention
• Unread new requests - Requests you haven't opened yet
• Unread new responses - Requests with data subject responses you haven't read
• All unread - All requests that are new, have new responses, or are manually marked as unread
• Autopilot error - Requests where automation encountered an issue Privacy Rights

Using pre-configured views

Under "Active requests" in your sidebar, you'll find ready-made views to help you navigate your unread queue:

• All open - Every active request in your queue
• Required attention - Requests flagged for urgent action
• Unread new requests - Requests you haven't entered yet
• Unread new responses - Requests with unread data subject replies
• All unread - The complete set of unread requests, including new requests, new responses, and manually marked items

How requests move between categories

Understanding how requests transition between categories helps you maintain an organized queue:

• When you mark a request as "Required attention," it immediately stops appearing in the new requests and new responses views. This is intentional—by flagging something for required attention, you're indicating that someone has already reviewed it and made a decision about its priority.

• Entering a new request removes it from the new requests category, regardless of whether you reply, take action, or simply exit after entering it. The same applies to new responses—once you enter a request with a new response, it's no longer categorized as having a new response.

• Manually marking a request as unread keeps it in the all unread view but doesn't retroactively make it appear as a new request or new response. Manual unread markers are a separate organizational tool that complements the automatic categorization.

Tips for managing your unread queue

👍 Start your day by checking the unread new requests view to handle fresh inquiries first. Then move to unread new responses to address ongoing conversations. Use the all unread view when you want a comprehensive picture of everything that needs attention.

👍 If you need to come back to a request later, mark it as unread manually or flag it as required attention, depending on the urgency. This ensures it stays visible in your queue until you're ready to address it fully.

👍 The filtering system works together with your existing workflow. You can still use search, sort options, and other filters in combination with unread categories to find exactly what you want.

Need Help?

If you have questions about unread requests, reach out to your MineOS CSM.