diff --git a/docs/guidelines/language/operational-emails/_category_.json b/docs/guidelines/language/operational-emails/_category_.json
new file mode 100644
index 000000000..0074c8839
--- /dev/null
+++ b/docs/guidelines/language/operational-emails/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Operational emails",
+  "position": 11
+}
diff --git a/docs/guidelines/language/operational-emails/general-information-and-administrative-emails.md b/docs/guidelines/language/operational-emails/general-information-and-administrative-emails.md
new file mode 100644
index 000000000..32d0098a8
--- /dev/null
+++ b/docs/guidelines/language/operational-emails/general-information-and-administrative-emails.md
@@ -0,0 +1,189 @@
+---
+sidebar_position: 7
+sidebar_label: General information and administrative emails
+title: General information and administrative emails
+doc-type: 'banner'
+description: 'In everyday operations, clear communication is key to maintaining transparency and trust. General notifications - covering administrative details, confirmations, and other essential updates outside specific operational categories - help keep stakeholders informed and processes organized. Well-structured messaging ensures clarity, reduces confusion, and supports smooth business interactions.'
+---
+
+#
+
+Note: Use these rules alongside the [General rules](#) and we have used [App name] as the standard placeholder for you to adapt individually to your product. All placeholders are shown with square brackets [placeholder].
+
+## Subject lines
+
+Use a subject line that accurately reflects the email's content and purpose.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- [App name] | New Terms of Use
+- [App name] | Changes to your data options
+- [App name] | Join our user testing
+- [App name] | Tell us about your app experience
+
+</div>
+</div>
+
+## Body text
+
+### Agreements and confirmation
+
+Be specific when asking for confirmation or agreement.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- You have to confirm the new Terms of Use until January 31, 2026.
+
+</div>
+<div className="donts" markdown="true">
+
+- Reading this email means you agree to our new Terms of Use.
+
+</div>
+</div>
+
+Include all relevant details of the agreement, order or change for the customer's records.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Your order for 5 “SINAMICS G120 Drives” (Order #QuantumShift Platform-2025-12345) has been received and processed. Estimated delivery: January 15, 2026.
+
+</div>
+</div>
+
+Avoid ambiguous phrasing that could lead to misunderstandings.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Your support contract for “Automation System S7-1500” has been renewed for one year, effective January 1, 2026.
+
+</div>
+<div className="donts" markdown="true">
+
+- We've extended your S7-1500 support.
+
+</div>
+</div>
+
+Include a method for the customer to review, modify or cancel the agreement or action if applicable.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- You can review your subscription details or manage your preferences at any time through your [App name] account dashboard: [link to dashboard].
+
+</div>
+</div>
+
+### Feedback and surveys
+
+Use a clear and polite invitation that explains the purpose of the survey.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- We value your opinion and would appreciate your feedback on your recent interaction with our technical support team.
+
+</div>
+</div>
+
+Include an estimate of the time required to complete the survey.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- This short survey will take approximately 5 minutes to complete.
+
+</div>
+</div>
+
+Include direct and secure links or buttons to make participation easier.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Share your thoughts via this secure link: [Link to survey].
+
+</div>
+<div className="donts" markdown="true">
+
+- Go to our website to find the survey.
+
+</div>
+</div>
+
+### Communication information
+
+Include specific reference numbers or identifiers to help users track issues.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- When contacting support, reference ticket ID: [App name]-2026-54321.
+
+</div>
+</div>
+
+Avoid hiding or making it difficult to find options for managing communication preferences or unsubscribing.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- You can manage your email preferences here: [link to preference center].
+- Unsubscribe from emails here.
+
+</div>
+</div>
+
+## Best practice example for New Terms of Use
+
+**Subject**<br/>
+[App name] | New Terms of Use
+
+**Body**
+
+Dear [App name] user,<br/>
+There is an update to the Terms of Use for your [App name] account.<br/>
+What you need to do<br/>
+To continue using [App name], read and agree to the new Terms of Use by January 31, 2026.
+
+Button: Open Terms of Use
+
+If you have any questions or need assistance, contact our team at [email address].
+
+Kind regards,<br/>
+Your [App name] team
+
+[Company disclaimer]<br/>
+[Company legal footer]
+
+## Best practice example for customer survey invitation
+
+**Subject**<br/>
+[App name] | Tell us about your app experience
+
+**Body**
+
+Dear [App name] user,<br/>
+We’ve put together a short survey to gather your thoughts on various aspects of [App name], such as usability, performance and features.<br/>
+You can participate in the anonymous survey by March 2, 2025.<br/>
+This short survey will take approximately 5–7 minutes to complete.
+
+Button: Participate in the survey
+
+Thank you for helping us improve [App name].<br/>
+If you have any questions or need assistance, contact our team at [email address].
+
+Kind regards,<br/>
+Your [App name] team
+
+[Company disclaimer]<br/>
+[Company legal footer]
+
+## Related
+
+- [Non-critical information messages](../messaging/non-critical-information-messages.mdx)
diff --git a/docs/guidelines/language/operational-emails/operational-emails-general-rules.md b/docs/guidelines/language/operational-emails/operational-emails-general-rules.md
new file mode 100644
index 000000000..17c893d40
--- /dev/null
+++ b/docs/guidelines/language/operational-emails/operational-emails-general-rules.md
@@ -0,0 +1,427 @@
+---
+sidebar_position: 1
+sidebar_label: General rules
+title: General rules
+doc-type: 'banner'
+description: 'In industrial applications, customer emails connect users to essential information, project updates and critical alerts. Well-written and clear customer emails keep operations running smoothly and users well-informed.'
+---
+
+#
+
+Note: We have used [App name] as the standard placeholder for you to adapt individually to your product. All placeholders are shown with square brackets [placeholder].
+
+Keep emails short, add relevant information and avoid complex and lengthy sentences.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Renew your license before December 31, 2026.
+
+</div>
+<div className="donts" markdown="true">
+
+- It is recommended by us that you renew your license before December 31 avoiding a possible delay in service.
+
+</div>
+</div>
+
+Use past tense for completed events.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Payment was processed Tuesday, November 11, 2025.
+
+</div>
+<div className="donts" markdown="true">
+
+- Payment is processing Tuesday, November 11, 2025.
+
+</div>
+</div>
+
+Use future tense for upcoming actions or scheduled events.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- We will deploy firmware Version 5.3 on November 22.
+
+</div>
+<div className="donts" markdown="true">
+
+- We deploy firmware Version 5.3 on November 22.
+
+</div>
+</div>
+
+Use the present perfect passive tense (have been / done) for system-generated confirmations or assignments.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- You have been assigned the role of “Energy Analyst”.
+
+</div>
+<div className="donts" markdown="true">
+
+- The system assigned you the role of “Energy Analyst”.
+
+</div>
+</div>
+
+Use the past active tense when someone manually assigns a task or role.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- John Smith assigned the following task to you:
+
+</div>
+<div className="donts" markdown="true">
+
+- You have been assigned the following task by John Smith.
+
+</div>
+</div>
+
+Use sentence case in your emails (capitalize only the first word of a sentence or heading and any proper nouns).
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- What’s happening
+
+</div>
+<div className="donts" markdown="true">
+
+- What’s Happening
+
+</div>
+</div>
+
+Use typographic double quotation marks for opening quotes “ (Unicode U+201C) and for closing quotes ” (Unicode U+201D) instead of single marks for consistency.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- You have been assigned the role of “Energy Analyst”.
+
+</div>
+<div className="donts" markdown="true">
+
+- You have been assigned the role of ‘Energy Analyst’.
+
+</div>
+</div>
+
+## Subject lines
+
+Start the subject line with the application name. Use pipe separators to clearly structure the subject line and separate the product name, action and topic.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- [App name] | Version 2.0 available
+
+</div>
+<div className="donts" markdown="true">
+
+- New Version 2.0 available
+- [App name]: Version 2.0 available
+
+</div>
+</div>
+
+Include purpose and theme, avoiding generic or vague subject lines.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- [App name] | Scheduled maintenance November 10, 2026, at 11:00
+
+</div>
+<div className="donts" markdown="true">
+
+- [App name] | Maintenance soon
+
+</div>
+</div>
+
+Use language that reflects the urgency of the email and mention if action is required.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- [App name] | Immediate action required | Security vulnerability fix
+- [App name] | No action required | New events detected
+
+</div>
+<div className="donts" markdown="true">
+
+- [App name] | Security issues
+
+</div>
+</div>
+
+Keep the subject line as short as possible. Additional information should be provided in the body text.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- [App name] | Immediate action required | Update
+
+</div>
+<div className="donts" markdown="true">
+
+- [App name] | Immediate action required | Update from old Version 2.4 to new Version 2.5 due to security issues
+
+</div>
+</div>
+
+## Body text
+
+Start with a polite salutation using “Dear” followed by a comma (American English). Do not use gendered titles or gendered forms of address. Use the recipient’s name if available. If no name is available, use a neutral greeting. For German translations, Siemens AG employees and partners can follow the [German Brand Guide](https://brandville.siemens.com/en/design-elements/language/inklusive-und-gendergerechte-sprache) for inclusive language.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Dear [App name] user,
+- Dear John Schmidt,
+
+</div>
+<div className="donts" markdown="true">
+
+- Hi
+
+</div>
+</div>
+
+Repeat key words from the subject line in the body text.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Subject line: [App name] | Version 2.0 available<br/>
+  Body text: We’ve released Version 2.0 of [App name].
+
+- Subject line: [App name] | One-time PIN for verification<br/>
+  Body text: You requested a one-time PIN to verify your identity.
+
+</div>
+</div>
+
+Use clear headings for users to easily scan body text for important information.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Heading: What happened
+- Heading: What’s happening
+- Heading: What you need to do
+
+</div>
+</div>
+
+Include a professional and polite closing with a descriptive signature.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Kind regards,<br/>
+  Your [App name] team
+
+</div>
+<div className="donts" markdown="true">
+
+- Best wishes,<br/>
+  Your friendly [App name] team
+
+</div>
+</div>
+
+### Time-related information
+
+Include specific times, dates and time zones whenever relevant.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- The update will start automatically on November 10 between 02:00–04:00 CET (UTC+1).
+
+</div>
+<div className="donts" markdown="true">
+
+- The update will be next week.
+
+</div>
+</div>
+
+Include duration and instructions when applicable.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- The registration link is valid for 24 hours.
+- The PIN is valid for 15 minutes from the time you received this email.
+
+</div>
+</div>
+
+### Actions and links
+
+Include a clear message when users don’t have to do anything.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- What you need to do<br/>
+  You don’t need to do anything. We’ll inform you when the data migration is complete.
+
+</div>
+</div>
+
+Provide a clear call-to-action when user actions are needed.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- What you need to do<br/>
+  Restart your system after the update to ensure all changes take effect.
+
+</div>
+</div>
+
+Add minimal links, actions, or buttons in each email (we recommend one per email).
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- [Open App name] event list N
+
+</div>
+</div>
+
+If possible, provide call-to-actions in buttons instead of links.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Open dashboard (button)
+
+</div>
+</div>
+
+Use inline text links for additional information.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- For additional information, see [webpage].
+
+</div>
+</div>
+
+Use a full, live link when buttons are not possible in the email (see [External links and resources](../menu-functions-and-ui-labels/external-links-and-resources.md)).
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Open your dashboard
+- [App name].com/dashboard
+
+</div>
+<div className="donts" markdown="true">
+
+- {'https://example.com/'}[App name]
+
+</div>
+</div>
+
+### Responding options
+
+Include options for users to respond to or get support when possible.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- If you have questions or need support, contact us at [email address].
+
+</div>
+</div>
+
+Clearly state when an email is automated and cannot be replied to.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- This email is automated: Do not reply.
+- This is an automated email. Do not reply.
+
+</div>
+</div>
+
+### Disclaimer and footer
+
+Include a legal disclaimer, the company’s legal footer and any other required legal information.<br/>
+Check the correct legal text with your legal team.
+
+### Formatting
+
+Highlight important information but avoid excessive and mixed text formatting.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Review the attached maintenance report for details.
+
+</div>
+<div className="donts" markdown="true">
+
+- Review the attached **Maintenance Report** for details.
+
+</div>
+</div>
+
+Do not use emojis.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Welcome to [App name] – your energy management platform
+
+</div>
+<div className="donts" markdown="true">
+
+- We love you for joining us!!!! Welcome to the team ❤️ ❤️
+
+</div>
+</div>
+
+### General best practice example
+
+**Subject**
+[App name] | Scheduled maintenance November 10, 2026
+
+**Body**
+Dear [App name] user,<br/>
+
+What’s happeningy<br/>
+On Monday, November 10, between 02:00–04:00, we will perform system<br/>
+maintenance that will cause temporary service interruptions.<br/>
+What you need to do<br/>
+Restart your system after the maintenance window to apply all updates.<br/>
+If you have any questions or need assistance, contact our team at [email address].
+
+Kind regards,<br/>
+Your [App name] team
+
+[Company disclaimer]<br/>
+[Company legal footer]
+
+## Related
+
+- [Grammar](#)
+- [Punctuation](#)
+- [Time and time zones](../formatting/timezones.mdx)
+- [Time-related messages](../messaging/time-related-messages.mdx)
\ No newline at end of file
diff --git a/docs/guidelines/language/operational-emails/operative-alarms-and-events.md b/docs/guidelines/language/operational-emails/operative-alarms-and-events.md
new file mode 100644
index 000000000..65fead7eb
--- /dev/null
+++ b/docs/guidelines/language/operational-emails/operative-alarms-and-events.md
@@ -0,0 +1,197 @@
+---
+sidebar_position: 3
+sidebar_label: Operative alarms and system event emails
+title: Operative alarms and system event emails
+doc-type: 'banner'
+description: 'Critical notifications require careful communication. Emails about alarms and security events must inform users quickly while maintaining clarity and calm.'
+---
+
+#
+
+Note: Use these rules alongside the [General rules](#) and we have used [App name] as the standard placeholder for you to adapt individually to your product. All placeholders are shown with square brackets [placeholder].
+
+## Subject lines
+
+State reason and criticality of the email directly in the subject line.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- [App name] | Failure detected in Plant A
+- [App name] | Critical risk of cyberattack
+- [App name] | Threshold change for asset TG_1234
+
+</div>
+</div>
+
+Use language that reflects the urgency of the email and mentions if actions are required.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- [App name] | Immediate action required | Security vulnerability fix
+- [App name] | No action required | New events detected
+
+</div>
+<div className="donts" markdown="true">
+
+- [App name] | Security issue
+
+</div>
+</div>
+
+## Body texts
+
+Be as specific as possible and tell users exactly what happened (what, when, how).
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Critical alarm immediate attention required: Power supply failure detected in Plant A.
+  &nbsp;&nbsp;&bull; Power supply failure detected in Plant A.<br/>
+  &nbsp;&nbsp;&bull; Event details: Overload detected on Transformer T-102 at 14:35 (UTC+2)<br/>
+  &nbsp;&nbsp;&bull; Location: Nuremberg facility 32/A.
+
+</div>
+</div>
+
+Explain consequences and solutions about the event whenever possible.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Event: Overload detected on Transformer T-102 at 14:35 at Nuremberg facility.
+
+</div>
+</div>
+
+Avoid vague timing or unclear instructions.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Act immediately.
+
+</div>
+<div className="donts" markdown="true">
+
+- Act soon.
+
+</div>
+</div>
+
+Use clear, action-oriented instructions for users, avoiding words like may, should or recommend.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Switch to backup power and confirm system status in the portal.
+
+</div>
+<div className="donts" markdown="true">
+
+- You should switch to backup power when possible.
+- You may want to switch to an alternative power supply.
+
+</div>
+</div>
+
+Explain if and how users can resolve issues or act with links, buttons, and suggestions.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- No action required. The vulnerabilities have been located and logged. [Open Log files] for more details.
+
+</div>
+<div className="donts" markdown="true">
+
+- We found 1000 vulnerabilities! This means your plant is in danger!
+
+</div>
+</div>
+
+## Best practice example for alarm email
+
+**Subject**
+
+[App name] | Immediate action required | Batch threshold exceeded
+
+**Body**
+
+Dear [App name] user,
+
+Batch BTH-20260304-A127 threshold exceeded:
+
+- Parameter: Temperature
+- Current value: 87.3°C
+- Threshold limit: 85.0°C
+- Deviation: +2.3°C (+2.7%)
+- Duration: 00:03:47
+
+Batch details:
+
+- Batch ID: BTH-20260304-A127
+- Product line: Beverage Mixing Line 3
+- Product: Orange Juice Concentrate
+- Location: Plant A, Nuremberg facility
+- Time: 2026-03-04 08:55:21
+
+What you need to do
+
+- Open Batch list to stop processing or adjust thresholds.
+
+Button: Open Batch list
+
+If you have any questions or need assistance, contact our team at [email address].
+
+Kind regards,<br/>
+[App name] team
+
+[Company disclaimer]<br/>
+[Company legal footer]
+
+## Best practice example for cyberattack notification
+
+**Subject**
+
+[App name] | Immediate action required | Critical risk of cyber attacks
+
+**Body**
+
+Dear [App name] user,
+
+A new cyberattack has been detected in your monitored environment. Immediate attention is required.
+
+Event details
+
+- Attack type: Unauthorized access attempt
+- Location: Erlangen facility
+- Time: 2026-03-04 08:55:21
+
+What you need to do
+
+- Switch to backup security protocols immediately.
+- Confirm system status in the Security portal.
+- Review recent logs for suspicious activity.
+
+We will continue monitoring the system and provide updates as needed.
+
+Button: Open [App name]
+
+If you have any questions or need assistance, contact our team at [email address].
+
+Kind regards,<br/>
+Your [App name] team
+
+[Company disclaimer]<br/>
+[Company legal footer]
+
+## Related
+
+- [Dates](../formatting/date.mdx)
+- [Time and time zones](../formatting/timezones.mdx)
+- [Time related messages](../messaging/time-related-messages.mdx)
+- [Error messages](../messaging/error-messages.mdx)
+- [Warnings](../messaging/warning-messages.mdx)
+- [Non-critical information messages](../messaging/non-critical-information-messages.mdx)
diff --git a/docs/guidelines/language/operational-emails/reports-and-data-provisioning-emails.md b/docs/guidelines/language/operational-emails/reports-and-data-provisioning-emails.md
new file mode 100644
index 000000000..7f822feaa
--- /dev/null
+++ b/docs/guidelines/language/operational-emails/reports-and-data-provisioning-emails.md
@@ -0,0 +1,121 @@
+---
+sidebar_position: 5
+sidebar_label: Reports and data provisioning emails
+title: Reports and data provisioning emails
+doc-type: 'banner'
+description: 'Well-written notifications about the completion and availability of generated reports or imported data ensure stakeholders can act quickly and confidently.'
+---
+
+#
+
+Note: Use these rules alongside the [General rules](#) and we have used [App name] as the standard placeholder for you to adapt individually to your product. All placeholders are shown with square brackets [placeholder].
+
+## Subject lines
+
+Use precise and descriptive subject lines that immediately convey the email's purpose.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- [App name] | Production efficiency report October 2025 available
+- [App name] | Test report available
+- [App name] | CSV import complete
+
+</div>
+</div>
+
+## Body text
+
+Use the full name of the report, dataset, or type of data being imported or migrated.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- The monthly "Q3 2025 energy consumption optimization report" is now available.
+- The import of your "Product inventory csv" is complete.
+
+</div>
+<div className="donts" markdown="true">
+
+- Your report is ready.
+
+</div>
+</div>
+
+Include a brief summary or key highlights from the report, especially if it's a regular deliverable.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- This month's "Performance overview" highlights a 5% improvement in uptime for production line 2 due to recent sensor recalibrations.
+
+</div>
+</div>
+
+Include the reporting period or relevant dates for the data covered in the report.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- The "Asset utilization report" for November 1–15, 2025 has been generated and is ready for your review.
+
+</div>
+</div>
+
+Include direct links to the report or data, minimizing steps for the user.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Your "Predictive maintenance analytics report" is available.<br/>
+  Button: [Open report]
+
+- The migrated "historical maintenance logs" are now fully accessible within Maintenance history.<br/>
+  Button: [Open Maintenance history]
+
+</div>
+</div>
+
+Use "you" and "your" for information or actions that are recipient-specific. Use neutral wording for shared or generally available information.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- The monthly "Energy consumption report" is now available.
+- Your requested "Product inventory csv" has been imported and is available to download.
+
+</div>
+</div>
+
+## Best practice example for report available
+
+**Subject**
+
+[App name] | Production efficiency report for October 2025
+
+**Body**
+
+Dear [App name] user,
+
+Your monthly production efficiency report for October 2025 is now available. This report provides a detailed overview of your operational performance, including key metrics for production line 1.
+
+Key highlights from October
+
+- Overall equipment effectiveness: Increased by 3.5%, driven by reduced unplanned downtime.
+- Downtime analysis: Minor stoppages decreased by 15%, indicating improved machine health.
+- Energy consumption: 2% reduction in energy usage per unit produced, reflecting optimization efforts.
+
+Button: Open report
+
+If you have any questions or need assistance, contact our team at [email address].
+
+Kind regards,<br/>
+Your [App name] team
+
+[Company disclaimer]<br/>
+[Company legal footer]
+
+## Related
+
+- [Error messages](../messaging/error-messages.mdx)
+- [Dates](../formatting/date.mdx)
diff --git a/docs/guidelines/language/operational-emails/system-and-product-lifecycle-emails.md b/docs/guidelines/language/operational-emails/system-and-product-lifecycle-emails.md
new file mode 100644
index 000000000..d778468b1
--- /dev/null
+++ b/docs/guidelines/language/operational-emails/system-and-product-lifecycle-emails.md
@@ -0,0 +1,190 @@
+---
+sidebar_position: 6
+sidebar_label: System and product lifecycle emails
+title: System and product lifecycle emails
+doc-type: 'banner'
+description: 'In complex systems and product ecosystems, actionable and structured lifecycle notifications are critical for maintaining stability and performance.'
+---
+
+#
+
+Note: Use these rules alongside the [General rules](#) and we have used [App name] as the standard placeholder for you to adapt individually to your product. All placeholders are shown with square brackets [placeholder].
+
+## Subject lines
+
+Include system or product lifecycle events, such as upcoming updates, directly in the subject line.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- [App name] | Version 2.0 available
+- [App name] | End-of-life announcement for "legacy control panel model X-200"
+- [App name] | Test version 2.1 available for staging environment
+- [App name] | Scheduled maintenance September 24, 2026, 01:00–13:00
+
+</div>
+</div>
+
+## Body text
+
+### Version and release announcements
+
+Include the new version number and release date.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Version 2.1.0 will be available starting November 10.
+
+</div>
+</div>
+
+Add a summary of key changes or improvements.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- This release includes enhanced firewall rules and improved logging.
+
+</div>
+</div>
+
+Include installation or update instructions with clear links, buttons or next steps.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Download the update via the [App name] portal and restart your system.<br/>
+  Button: Open [App name]
+
+</div>
+</div>
+
+### End-of-life announcements
+
+Include upgrade paths, migration guides and support options for product transitions.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Our dedicated support team is available to assist with your migration to the "smart factory OS". Contact us at [email address] or visit our [Migration portal].
+
+</div>
+</div>
+
+Use absolute terms when describing the end of a product status or availability.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Industrial Gateway V7.2 will no longer receive security updates after June 30, 2026.
+- Be advised that support for "control panel X-200" will officially end on December 31, 2026. Migrate to "control panel Z-200" for continued support and enhanced features.
+
+</div>
+</div>
+
+### Release approvals
+
+Include a clear request for approval.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Review and approve release V2.1.0 by November 10, 2026.
+
+</div>
+</div>
+
+Use links or attachments for release notes.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- See attached release documentation for full details.
+
+</div>
+</div>
+
+### Staging and test releases
+
+Include the test environment details.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- The staging release is now available at [web address]
+
+</div>
+</div>
+
+Use instructions for feedback or reporting issues.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Report any anomalies via the quality portal.
+- Send your feedback to [email address] by September 22, 2026.
+
+</div>
+</div>
+
+### Maintenance announcements
+
+Include the maintenance window and impact.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Scheduled maintenance will occur on Nov 15, 02:00–04:00. Temporary downtime expected.
+
+</div>
+</div>
+
+Use instructions for preparation or follow-up.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Ensure backups are completed before the maintenance window.<br/>
+  Button: Open [App name] drive manager
+
+</div>
+</div>
+
+## Best practice example for new version
+
+**Subject**
+
+[App name] | Version 2.1.0 available
+
+**Body**
+
+Dear [App name] user,
+
+We’re excited to announce the release of Version 2.1.0.
+
+What’s new
+
+- Enhanced firewall rules for improved security
+- Better logging for system diagnostics
+
+What you need to do
+
+- Download the update via the [App name] portal
+- Restart your system to apply changes
+
+Button: Open [App name]
+
+If you have any questions or need assistance, contact our team at [email address].
+
+Kind regards,<br/>
+Your [App name] team
+
+[Company disclaimer]<br/>
+[Company legal footer]
+
+## Related
+
+- [Version](../formatting/software-versions.mdx)
+- [Onboarding](../menu-functions-and-ui-labels/onboarding.md)
+- [What’s new announcements](../menu-functions-and-ui-labels/whats-new-announcements.md)
diff --git a/docs/guidelines/language/operational-emails/user-and-access-management-emails.md b/docs/guidelines/language/operational-emails/user-and-access-management-emails.md
new file mode 100644
index 000000000..b180c11e3
--- /dev/null
+++ b/docs/guidelines/language/operational-emails/user-and-access-management-emails.md
@@ -0,0 +1,181 @@
+---
+sidebar_position: 2
+sidebar_label: User and access management emails
+title: User and access management emails
+doc-type: 'banner'
+description: 'Clear, timely communication related to account creation, role assignments, invitations, onboarding and membership keep users informed and processes efficient.
+'
+---
+
+#
+
+Note: Use these rules alongside the [General rules](#) and we have used [App name] as the standard placeholder for you to adapt individually to your product. All placeholders are shown with square brackets [placeholder].
+
+## Subject lines
+
+State the clear purpose or topic of the email.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- [App name] | Welcome to [App name]
+- [App name] | Log in from new device
+- [App name] | Notification of role change
+- [App name] | One-time PIN for verification
+
+</div>
+</div>
+
+## Body text
+
+Start with a clear sentence describing the topic of the email.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Thank you for choosing [App name].
+- Your account has been successfully created.
+- You requested a one-time PIN to verify your identity.
+- A new device has been registered to this account: [{'user@example.com'}]
+
+</div>
+</div>
+
+Provide users with additional information or a summary.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- What you need to do<br/>
+	&nbsp;&nbsp;&bull; Open [App name]<br/>
+	&nbsp;&nbsp;&bull; Start configuring your dashboard<br/>
+	&nbsp;&nbsp;&bull; Explore key features: Real-time energy monitoring, load optimization and predictive analytics
+
+Button: Open
+
+</div>
+</div>
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+- The information below relates to your newly registered device:<br/>
+	&nbsp;&nbsp;&bull; Device name: Laptop123
+	&nbsp;&nbsp;&bull; Device ID: ABCDEFGHI
+	&nbsp;&nbsp;&bull; Operating system: Windows
+	&nbsp;&nbsp;&bull; Date: November 11, 2026, 14:32
+
+</div>
+</div>
+
+Provide users with clear next steps or instructions.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- You are just a few steps away from starting your [App name] journey. To get started, register for an [App name] ID using your email address and create a strong, secure password.
+
+</div>
+</div>
+
+Never include sensitive information such as passwords directly in the email.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- To set your password securely, visit the [App name] account portal.
+
+</div>
+<div className="donts" markdown="true">
+
+- Here is your default password: 12345 – change it here!
+
+</div>
+</div>
+
+Mention both previous and new states when access or role settings are changed.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- There have been changes to your role for [App name]:<br/>
+	New role: Administrator<br/>
+	Previous role: Operator
+
+</div>
+</div>
+
+## Best practice example for onboarding
+
+**Subject**
+[App name] | Welcome to [App name]
+
+**Body**
+Dear [App name] user,<br/>
+Welcome to [App name]. Your account has been successfully created and is ready to use.<br/>
+Your access credentials<br/>
+- Role assigned: Energy Analyst<br/>
+- Tenant ID: [App name] NBG_001<br/>
+What you need to do<br/>
+- Open [App name]<br/>
+- Start configuring your dashboard<br/>
+- Explore key features: Real-time energy monitoring, load optimization, and predictive analytics
+
+Button: Open
+
+To set your password securely visit our [App name portal]. For your safety, we never include passwords directly in emails.<br/>
+If you have any questions or need assistance, contact our team at [email address].
+
+Kind regards,<br/>
+Your [App name] team
+
+[Company disclaimer]<br/>
+[Company legal footer]
+
+## Best practice example for role changes
+
+**Subject**
+[App name] | Notification of role change
+
+**Body**
+Dear [App name] user,<br/>
+There have been changes to your role for [App name]:<br/>
+New role: Administrator<br/>
+Previous role: Operator<br/>
+To see your current role, log in and go to your profile.
+
+Button: Open
+
+Kind regards,<br/>
+Your [App name] team
+
+[Company disclaimer]<br/>
+[Company legal footer]
+
+## Best practice example for new devices
+
+**Subject**
+[App name] | Registered new device
+
+**Body**
+Dear [App name] user,<br/>
+A new device has been registered to your account: [{'user@example.com'}]<br/>
+Device name: Laptop123<br/>
+Device ID: ABCDEFGHI<br/>
+Operating system: Windows<br/>
+Date: November 11, 2026 at 14:32
+
+Review your registered devices here: [Link]
+
+If you haven't registered this device on your account, reach out to your local cybersecurity contact and ask them to open an investigation.<br/>
+Thank you for your cooperation.
+
+Kind regards,<br/>
+Your [App name] team
+
+[Company disclaimer]<br/>
+[Company legal footer]
+
+## Related
+- [Dates](../formatting/date.mdx)
+- [Time and time zones](../formatting/timezones.mdx)
+- [Time-related messages](../messaging/time-related-messages.mdx)
diff --git a/docs/guidelines/language/operational-emails/workflow-and-task-management-emails.md b/docs/guidelines/language/operational-emails/workflow-and-task-management-emails.md
new file mode 100644
index 000000000..c530aed34
--- /dev/null
+++ b/docs/guidelines/language/operational-emails/workflow-and-task-management-emails.md
@@ -0,0 +1,216 @@
+---
+sidebar_position: 4
+sidebar_label: Workflow and task management emails
+title: Workflow and task management emails
+doc-type: 'banner'
+description: 'Easily scannable and well-structured emails for workflow notifications help teams collaborate better and make faster decisions.'
+---
+
+#
+
+Note: Use these rules alongside the [General rules](#) and we have used [App name] as the standard placeholder for you to adapt individually to your product. All placeholders are shown with square brackets [placeholder].
+
+## Subject lines
+
+State clear purpose or topic of the email with a descriptive title for context.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- [App name] | Task #234 created | Spare part maintenance
+- [App name] | Task #659 assigned to you | Log file management
+- [App name] | Task #012 completed | Turbine overhaul
+- [App name] | Maintenance scheduled for Nov 11, 2026, 10:00
+
+</div>
+</div>
+
+State any time urgency, criticality or workflow impact within the subject line.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- [App name] | Immediate action required | Firmware update
+- [App name] | Task #134 | Review due Nov 11, 2026, 14:30
+- [App name] | Task #879 | Approval requested
+- [App name] | Task #987 | Overdue
+
+</div>
+</div>
+
+## Body text
+
+Use clear and unambiguous headings to tell users what needs to be managed.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Task assigned
+- Approval required
+- Task overdue
+- Review required
+
+</div>
+<div className="donts" markdown="true">
+
+- Task for you
+- Task
+
+</div>
+</div>
+
+Include bullet points to enhance readability and highlight key information.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- New task assigned<br/>
+ &nbsp;&nbsp;&bull; Task ID: 462<br/>
+ &nbsp;&nbsp;&bull; Task description: Spare part replacement for sensor 672_A<br/>
+ &nbsp;&nbsp;&bull; Assigned by: Operator<br/>
+ &nbsp;&nbsp;&bull; Assigned: February 10, 2026<br/>
+ &nbsp;&nbsp;&bull; Due: February 15, 2026
+
+</div>
+</div>
+
+Avoid vague statements about impact or required actions.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- This update will require a restart and cause 5 minutes of downtime for "[Asset name]".
+
+- Software update<br/>
+&nbsp;&nbsp;&bull; Software: Update to version 4.3.6<br/>
+&nbsp;&nbsp;&bull; Date: November 10, 2025<br/>
+&nbsp;&nbsp;&bull; Time: 01:00–01:05 (UTC+2)<br/>
+&nbsp;&nbsp;&bull; Impact: Brief downtime (approx. 5 minutes)
+
+</div>
+<div className="donts" markdown="true">
+
+- This update might require a restart.
+
+</div>
+</div>
+
+## Task management and progress
+
+Include specific and quantifiable progress updates whenever possible.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Software patch deployment for SCADA system is 75% complete.
+- Maintenance for "[Production Line 3]" is currently underway, estimated completion in 2 hours (10:00 UTC+2).
+
+</div>
+</div>
+
+Include expected completion times or clear next steps.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Expected completion by November 10, 2025, 22:00 (UTC+2). You will receive a notification once the system is fully operational.
+
+</div>
+</div>
+
+## Status updates
+
+Use clear indicators (operational, degraded, offline, standby) and state the impact immediately.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Status update | Remote monitoring system | Degraded performance
+- Status update | Conveyor belt system | Offline
+- Status update | Backup generator | Standby
+
+</div>
+</div>
+
+Avoid sending repetitive updates or leaving long gaps without communication during critical incidents. Only mention the previous status when it adds useful content.
+
+<div className="dos-and-donts" markdown="true">
+<div className="dos" markdown="true">
+
+- Ticket #274 status changed from "active" to "closed".
+- We will provide an update every 2 hours until resolution, or sooner if the status changes significantly. Our next update is scheduled for 14:00 (UTC+2).
+
+</div>
+</div>
+
+## Best practice example for task assignment
+
+**Subject**
+
+[App name] | Task #234 assigned to you
+
+**Body**
+
+Dear [App name] user,
+
+Task assigned
+
+- Task ID: 462
+- Task description: Spare part replacement for sensor 672_A
+- Assigned by: Operator
+- Assigned: February 10, 2026
+- Due date: February 15, 2026
+
+What you need to do
+
+Open Task list for further task details.
+
+Button: Open task list
+
+If you have any questions or need assistance, contact our team at [email address].
+
+This email is automated: Do not reply.
+
+Kind regards,<br/>
+Your [App name] team
+
+[Company disclaimer]<br/>
+[Company legal footer]
+
+## Best practice example for overdue task reminder
+
+**Subject**
+
+[App name] | Immediate action needed | Overdue task #1234 "Firmware update"
+
+**Body**
+
+Dear [App name] user,
+
+Overdue task
+
+- Task: Firmware update V5.6.01
+- Due: November 22, 2025
+
+What you need to do
+
+- Log in and perform update in Task manager
+
+Button: Open Task manager
+
+If you have any questions or need assistance, contact our team at [email address].
+
+This email is automated: Do not reply.
+
+Kind regards,<br/>
+Your [App name] team
+
+[Company disclaimer]<br/>
+[Company legal footer]
+
+## Related
+
+- [Time-related messages](../messaging/time-related-messages.mdx)
+- [Progress updates](../messaging/progress-updates.mdx)
+- [Dates](../formatting/date.mdx)
+- [Time and time zones](../formatting/timezones.mdx)