Comments
Suggested Enhancement ScopeTo minimize implementation impact while maximizing flexibility, we propose:1. Organization-Wide Default Setting (Primary Requirement) Allow administrators to define a default font family and size for the Rich Text Editor across the organization. This ensures consistent formatting with minimal behavioral changes.2. Rich Text Editor Default Configuration (Optional / Advanced) Allow configuration of default font settings at the Rich Text Editor control level, enabling:Different defaults per entity (Email, Case, Knowledge Article)Different defaults per field (optional)Future extensibility without breaking existing behaviorThis approach minimizes impact while providing long-term flexibility and maintainability.
Main purpose: Enable organization-wide default house style to ensure consistent formatting, accessibility compliance, and professional communication across all emails and rich text fields.Need : reasonably high , we now have to select all communication in de edtior before sending, Go way down in the font pulldown (no first letter press support) and then select our size. Editor easily shifts back to Segoe UI 9 which is NOT our standard. Gives user the idea that de editor is working faulty
Expanding on this idea, could we allow recipients to opt into specific notification types so each email address only receives the notifications they want?Example configurationEmail 1 — Opted in to Environment Update only (subset: Production / Sandbox)Email 2 — Opted in to Environment Update and Extension CompatibilityEmail 3 — Opted in to All notifications (current behaviour)This would allow only relevant alerts to be received by the right people and reduce noise while preserving the existing all‑alerts option for tenant admins.