AI agents: the content index is at /llms.txt. Every page is also available as Markdown — send the request header Accept: text/markdown, or append .md to the page URL.
We use necessary cookies (opens in a new tab) to run our website and improve your experience while browsing. Additional cookies are only used with your consent. You may revoke your consent on the Cookies Policy (opens in a new tab) page or in your browser at any time.
Is this really the version you are looking for? Kentico Xperience 12 Service Pack Documentation is no longer updated. Use the switcher in the header to choose your product version.
When a page reaches a workflow step, the system can send out notification email messages to those involved in the workflow process. This topic describes how to enable email notifications:
The topic applies to both basic and advanced workflow.
The emails are based on global email templates. Kentico comes with several default templates, which you can use without any additional configuration. If you want to create your own email templates for workflow notifications, follow the instructions in the Writing workflow email templates section.
The system sends notification emails according to the following rules:
When a page reaches a step (except Edit, Published and Archived), the Waiting for approval email is sent to users allowed to approve or reject the current (new) step.
When someone approves a page, i.e., moves it from an approval step to the next step, the Approved email is sent to the user who submitted the page for approval.
When someone rejects a page, i.e, moves it to the previous step, the Rejected email is sent to the user who submitted the page for approval.
Emails are never sent to users who performed the action that invoked the sending.
The system sends all workflow emails to users who have the Manage workflow permission, regardless of the settings on the Security tab of a custom workflow step.
Enabling workflow email notifications globally
Open the Settings application.
Navigate to Content -> Content management.
Turn the Send workflow emails setting on.
Type an address into the Send workflow emails from setting. This address will appear to recipients as the sender of the e‑mails.
Click Save.
Configuring email notifications for a workflow
Edit () the workflow and switch to the Emails tab.
Set the Send notification emails setting to Yes. Alternatively, you can Use site settings.
Check the box next to events that you want users to be notified about:
Send waiting for approval - sends an email when a page reaches an approval step (i.e. all steps except Edit, Published and Archived).
Send approved - sends an email when a page leaves an approval step in the direction towards the end of the workflow process.
Send rejected - sends an email when a page leaves a step in the direction towards the beginning of the workflow process.
Send published - sends an email when a page reaches a Published step.
Send archived - sends an email when a page reaches an Archived step.
(Optional) Select an email template for events for which you don't want to use the default template.
To bring up the list of available templates, click Select.
To edit the currently selected template, click Edit.
To create a new template, click New.
To clear your template selection and revert back to the default template, click Clear.
(Optional) Specify whether you want to notify users who are not involved in the process. This notification will be sent every time a page reaches a step that needs to be manually approved.
Select users using the Add users button.
(Optional) Select an email template. Otherwise, the default template will be used.
Click Save.
Configuring email notifications for a particular custom workflow step
You can configure email notifications for particular custom workflow steps.
Choose events you want users to be notified about.
Send waiting for approval - sends an email when a page reaches the step.
Send approved - sends an email when a page leaves the step in the direction towards the end of the workflow process.
Send rejected - sends an email when a page leaves the step in the direction towards the beginning of the workflow process.
(Optional) Select an email template for events for which you don't want to use the default template.
To bring up the list of available templates, click Select.
To edit the currently selected template, click Edit.
To create a new template, click New.
To clear your template selection and revert back to the default template, click Clear.
Click Save.
Writing workflow email templates
Open the Email templates application.
In the Site drop-down list, select global.
Click New template.
Enter a name for the new template into the Display name field.
Choose Workflow from the Email type drop-down list. This ensures that you will have relevant macros available to insert into the template's text.
(Optional) Specify a sender, a recipient, copy and blind copy recipients and a subject (From, Cc, Bcc and Subject fields).
Write the text of the template.
An email template can have two formats - HTML and plain text. You should write the template text at least in the format that you use on you websites. By default, the system sends HTML emails. You can find out what your settings are in Settings -> System -> Emails -> Email format. You can insert context-specific information into the template's text, such as the current step name or the link to edit the page, using macros. See the following section for a list of available macros.
Click Save.
Macros in workflow email templates
In email templates of the Workflow type, you can use macros that hold information about the workflow and about the page that invoked sending the email. The following list presents workflow-related macros that you can use:
ActionDefinition - object that holds the parameters of the current step, if the current step is an action step.
ApplicationURL - URL address of the application.
Comment - comment that users can add when approving or rejecting pages.
CurrentStep - object that holds data of the step the page is currently in.
CurrentUser - object that holds data of the currently logged in user.
Document - object that holds data of the page.
DocumentPreviewUrl - address where anyone can view the latest version of the page as it would appear on the live site.
DocumentEditUrl - address pointing to the page in the Pages application where editors can modify the page.
DocumentActionName - name of the action that was performed with the page. The macro has four possible values.
Approve
Archive
Publish
Reject
OriginalStep - object that holds data of the step the page was in before it was moved to the current step.
Workflow - object that holds data of the workflow process.
Besides the listed macros, you can also use any other macro expression, as described in the Macro expressions chapter.