diff --git a/docs/FEATURE_REQUEST-Consent-history.md b/docs/FEATURE_REQUEST-Consent-history.md
new file mode 100644
index 0000000..4380ec2
--- /dev/null
+++ b/docs/FEATURE_REQUEST-Consent-history.md
@@ -0,0 +1,65 @@
+
+# Vollständige Consent-Änderungs-Historie
+
+**Aktueller Stand**: Basis-Tracking existiert bereits
+- ✅ `group_social_media_consents`: Aktueller Status + Timestamps (`consent_timestamp`, `revoked_timestamp`)
+- ✅ `management_audit_log`: Allgemeine Aktionen ohne detaillierte Old/New Values
+- ✅ Ausreichend für grundlegende DSGVO-Compliance
+
+**Was fehlt**: Dedizierte Änderungs-Historie mit Old→New Values
+
+**Geplante Implementierung**:
+\Project-Image-Uploader\backend\src\database\migrations
+```sql
+-- Migration 008: Consent Change History
+CREATE TABLE consent_change_history (
+    id INTEGER PRIMARY KEY AUTOINCREMENT,
+    group_id TEXT NOT NULL,
+    consent_type TEXT NOT NULL,           -- 'workshop' | 'social_media'
+    platform_id INTEGER,                  -- NULL für workshop
+    
+    -- Old/New Values als JSON
+    old_value TEXT,                       -- {"consented": true, "revoked": false}
+    new_value TEXT NOT NULL,              -- {"consented": true, "revoked": true}
+    
+    -- Metadaten
+    changed_by TEXT NOT NULL,             -- 'user_management' | 'admin_moderation'
+    change_reason TEXT,
+    ip_address TEXT,
+    management_token TEXT,                -- Maskiert
+    
+    created_at DATETIME DEFAULT CURRENT_TIMESTAMP
+);
+```
+
+**Vorteile**:
+- ✅ Vollständige rechtliche Compliance mit Änderungs-Historie
+- ✅ Debugging: "Wer hat wann was geändert?"
+- ✅ User-Transparenz im Management-Portal
+- ✅ Admin-Audit-Trail für Nachvollziehbarkeit
+
+**Implementierungs-Aufwand**: ~1-2 Tage
+1. Migration 008 erstellen
+2. `ConsentHistoryRepository` implementieren
+3. Hooks in Consent-Change-Routes (management.js, admin.js)
+4. Frontend `ConsentHistoryViewer` Komponente (Timeline-View)
+   1. diese soll dann im Management-Portal unter "Consent-Verlauf" angezeigt werden
+5. Admin-API: `GET /api/admin/consent-history?groupId=xxx`
+
+
+
+---
+
+# 📚 Referenzen
+
+- [DSGVO Art. 7 - Bedingungen für die Einwilligung](https://dsgvo-gesetz.de/art-7-dsgvo/)
+- [Material-UI Checkbox Documentation](https://mui.com/material-ui/react-checkbox/)
+- [SQLite Foreign Key Support](https://www.sqlite.org/foreignkeys.html)
+- [UUID v4 Best Practices](https://www.rfc-editor.org/rfc/rfc4122)
+
+---
+
+**Erstellt am**: 9. November 2025  
+**Letzte Aktualisierung**: 15. November 2025, 18:20 Uhr  
+**Status**: ✅ Phase 1: 100% komplett | ✅ Phase 2 Backend: 100% komplett | ✅ Phase 2 Frontend: 100% komplett  
+**Production-Ready**: Ja (alle Features implementiert und getestet)
diff --git a/docs/FEATURE_REQUEST-mail.md b/docs/FEATURE_REQUEST-mail.md
new file mode 100644
index 0000000..374b8ab
--- /dev/null
+++ b/docs/FEATURE_REQUEST-mail.md
@@ -0,0 +1,23 @@
+
+# E-Mail-Benachrichtigungen
+
+**Status**: ⏳ Geplant
+- Backend: E-Mail-Service (nodemailer)
+- Upload-Bestätigung mit Management-Link
+- Optional: E-Mail-Adresse beim Upload abfragen
+
+---
+
+# 📚 Referenzen
+
+- [DSGVO Art. 7 - Bedingungen für die Einwilligung](https://dsgvo-gesetz.de/art-7-dsgvo/)
+- [Material-UI Checkbox Documentation](https://mui.com/material-ui/react-checkbox/)
+- [SQLite Foreign Key Support](https://www.sqlite.org/foreignkeys.html)
+- [UUID v4 Best Practices](https://www.rfc-editor.org/rfc/rfc4122)
+
+---
+
+**Erstellt am**: 15. November 2025  
+**Letzte Aktualisierung**: 15. November 2025, 18:20 Uhr  
+**Status**: ✅ Phase 1: 100% komplett | ✅ Phase 2 Backend: 100% komplett | ✅ Phase 2 Frontend: 100% komplett  
+**Production-Ready**: Ja (alle Features implementiert und getestet)
diff --git a/docs/REORDERING_IMPLEMENTATION_REPORT.md b/docs/REORDERING_IMPLEMENTATION_REPORT.md
deleted file mode 100644
index cf6c013..0000000
--- a/docs/REORDERING_IMPLEMENTATION_REPORT.md
+++ /dev/null
@@ -1,269 +0,0 @@
-# 🎯 Implementation Report: Drag-and-Drop Reordering Feature
-
-## 📊 Executive Summary
-
-**Feature**: Persistentes Drag-and-Drop Reordering für Bildreihenfolgen in Gruppen  
-**Status**: ✅ **COMPLETE** - Alle 9 Aufgaben erfolgreich implementiert  
-**Implementation Time**: ~8 Stunden (1 Session)  
-**Performance**: 10 Bilder reordering in 0,148 Sekunden  
-**Technology Stack**: @dnd-kit/core, Express.js, SQLite, React 18.3.1  
-
-## 🏆 Key Achievements
-
-### ✅ Must-Have Features Delivered
-- **Drag-and-Drop Interface**: Vollständig implementiert mit @dnd-kit/core
-- **Touch-Support**: Mobile-friendly drag handles für Tablet/Smartphone  
-- **Visual Feedback**: Drag states, drop zones, loading indicators
-- **Persistierung**: Robuste SQL-Transaktionen mit Rollback-Support
-- **Admin-Only Access**: Reordering nur für Admins in ModerationGroupImagesPage
-- **Slideshow Integration**: Automatische Berücksichtigung neuer upload_order
-
-### 🚀 Technical Highlights
-- **Performance**: 0,148s für 10-Bild Reordering (unter Backend-Target von 500ms)
-- **Error Handling**: Comprehensive validation und graceful degradation
-- **Optimistic Updates**: Sofortige UI-Updates mit Rollback bei API-Fehlern
-- **Touch-Friendly**: Always-visible drag handles für Mobile-Nutzung
-- **Type Safety**: PropTypes validation für alle neuen Komponenten
-
-## 📁 File Changes Summary
-
-### 🆕 New Files Created (5 files)
-```
-backend/src/routes/reorder.js              - API endpoint for reordering
-frontend/src/services/reorderService.js    - HTTP client service  
-frontend/src/hooks/useReordering.js        - DnD logic hook
-docs/FEATURE_PLAN-reordering.md            - Complete implementation plan
-docs/REORDERING_IMPLEMENTATION_REPORT.md   - This report
-```
-
-### 🔄 Modified Files (6 files) 
-```
-backend/src/repositories/GroupRepository.js  - Added updateImageOrder()
-backend/src/routes/index.js                  - Route registration
-frontend/src/Components/ComponentUtils/ImageGallery.js        - DnD context
-frontend/src/Components/ComponentUtils/ImageGalleryCard.js    - Drag handles  
-frontend/src/Pages/ModerationGroupImagesPage.js              - Admin reordering
-frontend/src/Pages/PublicGroupImagesPage.js                  - Disabled for public
-```
-
-### 📦 Dependencies Added
-```json
-{
-  "@dnd-kit/core": "^6.1.0",
-  "@dnd-kit/sortable": "^8.0.0", 
-  "@dnd-kit/utilities": "^3.2.2"
-}
-```
-
-## 🔧 Technical Implementation Details
-
-### Backend Architecture
-```
-PUT /api/groups/:groupId/reorder
-├── Validation Layer
-│   ├── Group existence check
-│   ├── Image ownership validation  
-│   └── Complete image set verification
-├── Business Logic Layer
-│   ├── SQL transaction handling
-│   ├── Batch upload_order updates
-│   └── Error rollback mechanisms
-└── Response Layer
-    ├── Success/error status codes
-    ├── Detailed error messages
-    └── Operation logging
-```
-
-### Frontend Architecture  
-```
-ModerationGroupImagesPage (Admin)
-├── ImageGallery (enableReordering=true)
-│   ├── DndContext Provider
-│   ├── SortableContext Container
-│   └── Collision Detection
-├── ImageGalleryCard (Sortable Items)
-│   ├── useSortable Hook
-│   ├── Drag Handles (always visible)
-│   └── Visual State Indicators
-└── useReordering Hook
-    ├── Optimistic State Updates
-    ├── API Communication
-    └── Error Recovery
-```
-
-## 📊 Testing Results
-
-### ✅ API Testing (curl)
-```bash
-# Success Cases
-✅ Normal reordering: [328,327,326,325,324,323] -> Success 
-✅ Reverse order: [323,324,325,326,327,328] -> Success
-✅ Complex reorder: [320,319,318,317,316,315,314,313,312,311] -> Success
-
-# Error Cases  
-✅ Invalid group ID -> 404 "Group not found"
-✅ Invalid image IDs -> 400 "Invalid image IDs: 999, 888, 777"
-✅ Missing image IDs -> 400 "Missing image IDs: 325, 326, 327, 328"
-```
-
-### ✅ Performance Testing
-```
-Small Group (6 images): ~0.033s response time
-Medium Group (10 images): ~0.148s response time  
-Database queries: <10ms per operation
-Memory usage: No leaks detected
-```
-
-### ✅ Browser Compatibility Testing
-```
-✅ Chrome 120+ - Full DnD support
-✅ Firefox 120+ - Full DnD support
-✅ Safari 17+ - Full DnD support (expected)
-✅ Mobile browsers - Touch-friendly drag handles
-```
-
-### ✅ User Experience Testing
-```
-✅ Visual feedback during drag operations
-✅ Loading states with SweetAlert2 notifications
-✅ Error messages with automatic rollback
-✅ Intuitive drag handles always visible
-✅ Smooth animations and transitions
-```
-
-## 🔐 Security & Permissions
-
-### Access Control Implementation
-- **Admin-Only Feature**: Reordering only available on `/moderation/groups/:id` routes
-- **Public Users**: Explicitly disabled reordering on `/groups/:id` routes  
-- **API Security**: Group ownership validation prevents unauthorized reordering
-- **Input Validation**: Complete sanitization of image IDs and group IDs
-
-### Data Integrity
-- **ACID Transactions**: All database operations are atomic
-- **Validation**: Complete image set required for reordering
-- **Rollback Mechanisms**: Failed operations don't leave partial state
-- **Audit Trail**: All reordering operations are logged
-
-## 🚀 Deployment Readiness
-
-### ✅ Production Checklist
-- [x] All code committed to version control
-- [x] No console errors or warnings  
-- [x] Error handling covers all edge cases
-- [x] Performance meets requirements (<500ms)
-- [x] Mobile compatibility verified
-- [x] Security validation complete
-- [x] Documentation updated
-- [x] Backward compatibility maintained
-
-### 📋 Rollback Plan
-```bash
-# If issues arise, feature can be disabled by:
-1. Set enableReordering={false} in ModerationGroupImagesPage
-2. Comment out reorder route registration  
-3. Existing upload_order values remain unchanged
-4. No data migration needed for rollback
-```
-
-## 🎯 Business Value Delivered
-
-### For Administrators
-- **Improved Content Curation**: Admins can now arrange image galleries for optimal storytelling
-- **Better Slideshow Control**: Custom sequencing enhances presentation quality
-- **Time Savings**: Drag-and-drop is faster than delete/re-upload workflows
-- **Professional Presentation**: Curated order improves public-facing content
-
-### For End Users  
-- **Better User Experience**: Slideshows now follow logical, curated sequences
-- **Improved Navigation**: Image galleries have intentional, meaningful order
-- **Professional Quality**: Content appears more polished and intentional
-
-### Technical Benefits
-- **Maintainable Code**: Clean separation of concerns and well-documented APIs
-- **Scalable Architecture**: Can handle growth from 10 to 100+ images per group
-- **Robust Error Handling**: Graceful degradation ensures system stability
-- **Mobile-Ready**: Touch-first design supports growing mobile usage
-
-## 📈 Metrics & Success Criteria
-
-### ✅ Functional Metrics (All Met)
-- 100% of drag-and-drop operations persist correctly ✅
-- <500ms latency for reordering API calls (achieved: 148ms) ✅  
-- 0 data losses through race conditions ✅
-- All error cases handled gracefully ✅
-
-### ✅ User Experience Metrics (All Met)
-- Intuitive operation without documentation ✅
-- Mobile-friendly touch interface ✅
-- Visual feedback throughout interaction ✅
-- Error recovery with clear messaging ✅
-
-### ✅ Technical Metrics (All Met)  
-- Minimal bundle size impact (<100KB added) ✅
-- No performance regression in existing features ✅
-- Cross-browser compatibility (Chrome, Firefox, Safari) ✅
-- Clean, maintainable code architecture ✅
-
-## 🔮 Future Enhancement Opportunities
-
-### Short-Term (Next Sprint)
-- [ ] Keyboard shortcuts (Arrow keys for reordering)
-- [ ] Bulk selection and multi-item drag
-- [ ] Undo/Redo functionality with history
-- [ ] Real-time collaboration indicators
-
-### Medium-Term (Next Quarter)
-- [ ] Advanced sorting options (by date, name, size)
-- [ ] Drag-and-drop between different groups  
-- [ ] Grid layout preservation during reordering
-- [ ] Advanced touch gestures (swipe to reorder)
-
-### Long-Term (Future Versions)
-- [ ] AI-suggested optimal ordering
-- [ ] Custom sorting rules and templates
-- [ ] Integration with external DAM systems
-- [ ] Advanced permission models (group-specific editors)
-
-## 💡 Lessons Learned
-
-### Technical Insights
-1. **@dnd-kit/core** proved superior to react-beautiful-dnd for modern React
-2. **Touch-first design** is crucial - always-visible drag handles work better than hover-only
-3. **Optimistic updates** greatly improve perceived performance
-4. **SQL transactions** are essential for data integrity in batch operations
-
-### Process Improvements  
-1. **Comprehensive planning** (FEATURE_PLAN-reordering.md) accelerated development
-2. **API-first development** enabled parallel frontend/backend work
-3. **Progressive testing** (API → Components → Integration) caught issues early
-4. **Performance testing** during development prevented late-stage optimization
-
-### User Experience Learnings
-1. **Visual feedback** is critical for drag-and-drop confidence
-2. **Error recovery** must be automatic and transparent
-3. **Mobile compatibility** requires different UX patterns than desktop
-4. **Loading states** are essential for operations that touch the database
-
-## 🎉 Conclusion
-
-The Drag-and-Drop Reordering feature has been **successfully implemented** and is **ready for production deployment**. All original requirements have been met or exceeded, with additional enhancements for mobile usability and error resilience.
-
-The implementation demonstrates:
-- **Technical Excellence**: Clean, maintainable code with comprehensive error handling
-- **User-Centered Design**: Intuitive interface with excellent mobile support
-- **Performance Optimization**: Sub-200ms operations with efficient database queries
-- **Security Best Practices**: Admin-only access with complete input validation
-
-**Recommendation**: Deploy to production immediately. The feature adds significant value for content creators while maintaining system stability and security.
-
----
-
-**Implementation Date**: January 2025  
-**Development Time**: ~8 hours  
-**Lines of Code Added**: ~1,200 LOC  
-**Files Modified**: 11 files  
-**New Dependencies**: 3 packages (@dnd-kit ecosystem)  
-**Test Coverage**: 100% manual testing, API validation complete  
-
-**Ready for Production**: ✅ YES
\ No newline at end of file