Q1. What is an email template used for?
A template defines the recipient, timing, and content of a notification for events such as inactivity warnings, access removal, or account deactivation. Templates support merge-style variables (e.g., user name, product name, days remaining) to personalize each message.
Q2. Why must I pick a “rule” or link templates to scheduler rules?
Notifications are designed to work with automation rules such as cleanup or access removal. Only enabled rules from your scheduler configuration can send notifications, so each template must be linked to a specific rule.
Q3. What does “days before” (or similar) mean on a template?
This setting controls how far in advance of the rule's action the notification is sent, for example, how many days of inactivity must pass before the message is triggered. The value must be a positive number within the allowed range.
Q4. When do I need to select Jira Software, JSM, Confluence, or Bitbucket?
For templates related to product access removal, you must select at least one application so the email references the correct product. This also ensures variables like {{product_name}} display the right value.
Q5. How do preview and “test email” differ?
Preview displays the subject and body with sample values substituted for all variables. Test email sends an actual message to an address you specify, letting you verify delivery and formatting before going live.
Q6. Why didn’t my test email send?
Common causes include an invalid email address, an unsaved template, missing required fields, or backend mail limits. Check the toast notification that appears for the specific error message, and verify your token health or Settings if the problem persists.
