Major fix: Inbox only shows unapproved emails, not approved ones

Critical corrections to Inbox Management documentation:

Overview & Page Layout:
- Clarified: Inbox displays only UNAPPROVED emails
- Added callout: "Inbox Shows Only Unapproved Emails"
- Explained: Approved emails immediately disappear from inbox
- Inbox is a staging area for emails awaiting approval/deletion

Email Detail Modal - Metadata Section:
- REMOVED incorrect fields that don't exist for inbox emails:
  * "Customer: If already approved..." (approved emails aren't in inbox!)
  * "Approved: Checkmark..." (no checkmark - they disappear when approved!)
- Added list of action buttons (Approve, Re-parse, Delete, Download .eml)

What Happens After Approval:
- Changed "moved out of inbox" to "immediately disappears from inbox"
- Added: Future emails are "automatically approved and linked WITHOUT
  appearing in the inbox" - they go directly to operational views
- New callout: "Approved Emails Don't Return" explaining auto-approval flow

Inbox Filters and Search:
- Changed "all imported emails" to "all UNAPPROVED imported emails"

Common Workflows - Setting Up New Customer:
- Updated step 5: "approved emails disappear from inbox"
- Added step 6: Jobs appear in Jobs/Daily Jobs/Run Checks pages
- Updated step 7: Future reports auto-approved, never appear in inbox

This accurately reflects that the inbox is ONLY for unapproved emails.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

containers/backupchecks/src/templates/documentation/mail-import/inbox-management.html

@@ -33,7 +33,12 @@
 
 <h2>Inbox Page Layout</h2>
 
-<p>The Inbox page displays a table with all imported emails. Each row represents one email message.</p>
+<p>The Inbox page displays a table with all <strong>unapproved</strong> imported emails. Each row represents one email message that has not yet been approved.</p>
+
+<div class="doc-callout doc-callout-info">
+  <strong>💡 Inbox Shows Only Unapproved Emails:</strong><br>
+  Once you approve an email, it immediately disappears from the inbox and the job appears in operational views (Jobs, Daily Jobs, Run Checks). The inbox only contains emails awaiting approval or deletion.
+</div>
 
 <h3>Table Columns</h3>
 
@@ -121,10 +126,17 @@
   <li><strong>From:</strong> Sender address</li>
   <li><strong>Subject:</strong> Email subject</li>
   <li><strong>Received:</strong> Timestamp</li>
-  <li><strong>Backup software / Type / Job name:</strong> Parsed values</li>
+  <li><strong>Backup software / Type / Job name:</strong> Parsed values extracted from email content</li>
   <li><strong>Overall status:</strong> Success/Warning/Failed indicator</li>
-  <li><strong>Customer:</strong> If already approved and linked to a customer</li>
-  <li><strong>Approved:</strong> Checkmark if this email has been approved</li>
+</ul>
+
+<p>The metadata section also includes action buttons:</p>
+
+<ul>
+  <li><strong>Approve:</strong> Opens the approval dialog to link this email to a customer and create a job</li>
+  <li><strong>Re-parse:</strong> Re-runs parsers on this email to update parsed data</li>
+  <li><strong>Delete:</strong> Marks the email as deleted and removes it from the inbox</li>
+  <li><strong>Download .eml:</strong> Downloads the original email file (if stored)</li>
 </ul>
 
 <h4>2. Email Body (Middle)</h4>
@@ -215,11 +227,16 @@
   <li>A <strong>Job</strong> record is created in the database (if it doesn't already exist)</li>
   <li>A <strong>JobRun</strong> record is created, representing this specific backup run</li>
   <li><strong>JobObject</strong> records are created for each parsed object (VMs, servers, etc.)</li>
-  <li>The email is marked as <strong>approved</strong> and moved out of the inbox</li>
+  <li>The email is marked as <strong>approved</strong> and <strong>immediately disappears from the inbox</strong></li>
   <li>The job immediately appears in <strong>Jobs</strong>, <strong>Daily Jobs</strong>, and <strong>Run Checks</strong> pages</li>
-  <li>Future emails matching the same job are <strong>automatically linked</strong> without manual approval</li>
+  <li>Future emails matching the same job are <strong>automatically approved and linked</strong> without appearing in the inbox</li>
 </ol>
 
+<div class="doc-callout doc-callout-info">
+  <strong>💡 Approved Emails Don't Return:</strong><br>
+  Once approved, an email permanently leaves the inbox. Future emails for the same job are automatically approved during import and never appear in the inbox - they go directly to operational views.
+</div>
+
 <div class="doc-callout doc-callout-warning">
   <strong>⚠️ Job Matching:</strong><br>
   After approval, future emails are matched to this job based on sender address, job name, and backup software. If these change (e.g., job is renamed), you may need to approve a new email to create a new job record.
@@ -302,7 +319,7 @@
 
 <h2>Inbox Filters and Search</h2>
 
-<p>The inbox currently displays all imported emails in chronological order (newest first). Filtering and search features are planned for a future update.</p>
+<p>The inbox currently displays all <strong>unapproved</strong> imported emails in chronological order (newest first). Filtering and search features are planned for a future update.</p>
 
 <div class="doc-callout doc-callout-info">
   <strong>📝 Future Feature:</strong><br>
@@ -318,8 +335,9 @@
   <li>Wait for backup reports to arrive in the inbox (or trigger a manual import)</li>
   <li>Review each email for the customer in the inbox</li>
   <li>Approve each email, selecting the new customer from the dropdown</li>
-  <li>Jobs are now created and linked to the customer</li>
-  <li>Future reports are automatically linked without approval</li>
+  <li>The approved emails disappear from the inbox and jobs are created</li>
+  <li>Jobs now appear in <strong>Jobs</strong>, <strong>Daily Jobs</strong>, and <strong>Run Checks</strong> pages</li>
+  <li>Future backup reports are automatically approved and never appear in the inbox</li>
 </ol>
 
 <h3>Troubleshooting Unparsed Emails</h3>

docs/changelog-claude.md

@@ -7,7 +7,7 @@ This file documents all changes made to this project via Claude Code.
 ### Added
 - Completed Mail & Import documentation section (4 pages):
   - **Mail Import Setup**: Microsoft Graph API configuration with enhanced security (Azure AD app registration, start with Mail.Read only, Application Access Policy to restrict access to one mailbox via Exchange PowerShell, add Mail.ReadWrite after testing), two-step save workflow clarification (same "Save settings" button clicked twice - once for credentials to enable folder browsing, then again for complete configuration), automatic folder browser popup (no manual path entry), test configuration, troubleshooting (authentication errors, folder not found, no emails imported), advanced configuration (email retention, multiple mailboxes), comprehensive security best practices including principle of least privilege, note about planned UI improvement to make two-step save workflow more obvious
-  - **Inbox Management**: Inbox overview and workflow, table columns explanation (EML column shows download link, not checkmark), viewing email details with screenshot (approve-job.png showing metadata, body iframe, and approval interface), email detail modal sections (metadata, body iframe, parsed objects), approving emails (customer selection, job name), what happens after approval, re-parsing emails (single and bulk), deleting emails (single and bulk delete, soft delete behavior), downloading .eml files, common workflows (new customer setup, troubleshooting unparsed emails, cleaning spam), best practices
+  - **Inbox Management**: Inbox overview and workflow (inbox shows ONLY unapproved emails - approved emails immediately disappear), table columns explanation (EML column shows download link, not checkmark), viewing email details with screenshot (approve-job.png showing metadata, body iframe, and approval interface), email detail modal sections (metadata with action buttons, body iframe, parsed objects - removed incorrect "Customer" and "Approved" fields), approving emails (customer selection, job name), what happens after approval (email disappears from inbox, future emails auto-approved and never appear in inbox), re-parsing emails (single and bulk), deleting emails (single and bulk delete, soft delete behavior), downloading .eml files, common workflows (new customer setup with clear approval flow, troubleshooting unparsed emails, cleaning spam), best practices
   - **Mail Parsing**: Parsing overview and workflow (retrieval, preprocessing, parser selection, matching, parsing, storage), parsers (viewing available parsers, parser information), match criteria (sender, subject, body match), supported backup software (Veeam, Synology, NAKIVO, Boxafe, Panel3, QNAP, Syncovery, 3CX, RDrive, NTFS Auditing), parser execution order, enabling/disabling parsers, re-parsing emails, parsing workflow example, troubleshooting parsing issues, parser limitations, best practices
   - **Auto-Import Configuration**: Auto-import overview and features, enabling auto-import, import interval configuration (5/15/30/60 minutes), batch size explanation, how auto-import works (timer, check settings, authenticate, fetch, parse, auto-approve, move, log, persist, wait), auto-approval logic and conditions, when auto-approval fails, manual import (triggering, batch size 1-50), import settings summary table, monitoring import activity (audit log, inbox page, jobs/daily jobs), troubleshooting (auto-import not running, emails not auto-approved, import errors), best practices, advanced configuration (disabling temporarily, EML retention, high-volume environments)