Notification Templates

The Notification domain handles delivery of platform notifications. As a platform administrator, you define templates that control how messages look for each use case and channel.

Templates give you a clean separation between:

• When a notification is triggered (by domain logic)
• How the message is rendered (by your template)

Channels

The Control Plane supports three notification channel types:

Channel	Description
Email	Delivers notifications via email. Requires SMTP configuration.
MS Teams	Delivers notifications to Microsoft Teams channels via webhooks.
Webhook	Delivers notifications to any HTTP endpoint.

Automatic channel provisioning

When a team is created through the Organization domain, a NotificationChannel is automatically created for that team. You can configure channel details (recipients, webhook settings, filters) to control what each team receives.

How template selection works

At send time, the platform selects a template by combining:

• the notification purpose (for example, onboarded)
• the channel type suffix (for email channels this is mail)

So an onboarding email template is expected to be named:

onboarded--mail

If no matching template exists, the notification cannot be rendered.

Templates

A Notification Template defines how a notification for a specific purpose and channel type is formatted. Templates use placeholder variables that are filled in at delivery time.

apiVersion: notification.cp.ei.telekom.de/v1
kind: NotificationTemplate
metadata:
  name: approvalrequest--subscribe--created--decider--mail
  namespace: dev
spec:
  purpose: approvalrequest--subscribe--created--decider
  channelType: Email
  subjectTemplate: "[{{.environment}}] New subscription request for {{.resource_name}}"
  template: |
    Hello team {{.decider_team}},

    A new subscription request has been created by team {{.requester_team}}
    for {{.resource_type}} {{.resource_name}}.

    Please review and approve or reject the request.

Required fields

• metadata.name — must follow the lookup convention (<purpose>--<channelSuffix>)
• spec.purpose — event type that this template handles
• spec.channelType — Email, MsTeams, or Webhook
• spec.template — message body (text or HTML)
• spec.subjectTemplate — optional, but typically required for Email

Placeholders

Placeholders are dynamic values injected at delivery time.

Common examples:

• {{.environment}}
• {{.requester_team}}, {{.requester_group}}, {{.requester_application}}
• {{.decider_team}}, {{.decider_group}}, {{.decider_application}}
• {{.resource_type}}, {{.resource_name}}
• {{.state_old}}, {{.state_new}}
• {{.scopes}}

You can also use basic Go-template logic such as if and range.

Built-in purposes (default templates)

The installation component install/components/notificationtemplates ships templates for these built-in purposes:

Purpose	Typical trigger
approvalrequest--subscribe--created--decider	New subscription request created
approvalrequest--subscribe--updated--decider	Request state changed (decider view)
approvalrequest--subscribe--updated--requester	Request state changed (requester view)
approval--subscribe--updated--decider	Subscription updated (decider view)
approval--subscribe--updated--requester	Subscription updated (requester view)
onboarded	Team created
token-rotated	Team token rotated
team-members-changed	Team members updated

Enabling default templates

The default templates are provided as a Kustomize component.

1. Add the component to your overlay:

components:
  - ../../components/notificationtemplates

2. Apply your overlay:

kubectl apply -k install/overlays/local

Adjust the overlay path to match your installation model.

Recommended admin workflow

1. Start from defaults: enable the notification template component.
2. Brand safely: update wording, layout, and logos without changing purpose and template naming conventions.
3. Test in non-production: trigger an onboarding or approval flow and verify rendered output.
4. Promote with GitOps: version template changes like any other platform config.

Troubleshooting

• Notification exists but not delivered
  • Check that the team has a ready NotificationChannel.
• Template not found errors
  • Verify metadata.name matches <purpose>--<channelSuffix>.
  • Verify spec.purpose exactly matches the emitted purpose.
• Broken rendering / empty fields
  • Check placeholder names (they are case-sensitive).
  • Ensure the expected properties are provided by the source notification.

Next Steps

• Operations & Monitoring — Day-2 operational tasks
• Architecture: Notification Domain — Deep dive into the Notification domain