Skip to content

Commit b0cd8f3

Browse files
Create 2025-11-18-temporary-adjustment-to-final-disposition-column (cloudflare#26611)
* Create 2025-11-18-temporary-adjustment-to-final-disposition-column Explanation for temporary removal of submission status update column in UI * Update and rename 2025-11-18-temporary-adjustment-to-final-disposition-column to 2025-11-18-temporary-adjustment-to-final-disposition-column.mdx * Add files via upload * Add missing description --------- Co-authored-by: Pedro Sousa <[email protected]>
1 parent a22ec29 commit b0cd8f3

File tree

2 files changed

+23
-0
lines changed

2 files changed

+23
-0
lines changed
72.3 KB
Loading
Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
title: Temporary Adjustment to Final Disposition Column
3+
description: We have removed the final disposition column for submitted email misses as part of a revamp
4+
date: 2025-11-18
5+
---
6+
7+
# Temporary Adjustment to Final Disposition Column
8+
9+
To facilitate significant enhancements to our submission processes, the **Final Disposition** column of the **Team Submissions > Reclassifications** page inside the **Email Security Zero Trust** application will be temporarily removed.
10+
11+
---
12+
13+
### What's Changing
14+
15+
The column displaying the final disposition status for submitted email misses will no longer be visible on the specified page.
16+
17+
### Why We're Doing This
18+
19+
This temporary change is required as we revamp and integrate a more powerful backend infrastructure for processing these security-critical submissions. This update is designed to make even more effective use of the data you provide to improve our detection capabilities. We assure you that your submissions are continuing to be addressed at an even greater rate than before, fueling faster and more accurate security improvements.
20+
21+
### Next Steps
22+
23+
Rest assured, the ability to submit email misses and the underlying analysis work remain **fully operational**. We are committed to reintroducing a refined, more valuable status update feature once the new infrastructure is completed.

0 commit comments

Comments
 (0)