Notification Templates

Use Identity > Notification Templates to inspect, compare, edit, back up, copy, import, or export PingOne notification template configuration.

Common Uses

• Compare source and destination templates.
• Review localized template content.
• Copy templates to another environment or repository target.
• Back up templates before migration.
• Inspect normalized differences with CompareIQ where available.

Basic Workflow

1. Select an Org Root.
2. Select a source environment.
3. Optionally select a destination environment or repository target.
4. Search for the template.
5. Open the row to inspect details or edit supported fields.
6. Use copy or export actions when moving templates.

Compare and Copy

When source and destination are selected, review match indicators before copying. Template comparisons may normalize environment-managed metadata so IDs, links, environment references, and timestamps do not dominate the result.

Before copying:

• Confirm the destination environment.
• Review subject, body, locale, method, and group.
• Confirm the destination does not already contain a template that should be preserved.
• Export a backup where available.

Repository Use

Notification Templates can be loaded from or written to enabled repository targets. Make sure the repository source contains notification template files rather than mixed or unrelated domain files.

Troubleshooting

If templates do not appear, confirm:

• Source environment is selected.
• Worker app has identity read access.
• Filters are cleared.
• Repository path points to notification template content when using a repository source.