Available to Project Owner.
Each Step sends a Task Notification e-mail to the Collaborators assigned to it, and by default Leap writes that message for you. You can replace the subject, the greeting and the body with your own text for an individual Step. This would be useful when the people in that Step need context the standard wording cannot give them.
The custom message goes to every Collaborator in that Step. It is set per Step, so different Steps in the same Workflow can carry different messages.
Customize Notification Email
-
Open the Step Properties dialog. Either click a Step box, or click the [>] button on a Step box and then the Modify Step option.
-
Find the Notification Email section. It shows whether the Step is currently using Default content or Custom content.
-
Click [Customize] button.
-
In the Customize email dialog, click Custom.
Write the message
The Message preview on the right updates as you type, so you can see what recipients will receive before you save.
-
Email subject — the subject line of the e-mail.
-
Greetings — the opening line, in place of Leap’s default greeting.
-
Email body — your message to the Collaborators in this Step.
-
Optionally tick Include project title and task description to show the Project title and the Task description underneath your text, as the default e-mail does.
Click [Save] when you are done.
Only the subject, greeting and body are yours to write. The action button, the fallback link and the e-mail footer stay as they are.
After saving
The Notification Email section now reads Custom content, so you can tell at a glance which Steps have been personalized.
Return to the default message
-
Open the Customize email dialog again.
-
Click Default.
-
Click [Save].
The Step goes back to Leap’s standard notification.
Custom messages and Guest Collaborator language
A custom message is sent exactly as you wrote it, in the language you wrote it in. Therefore, it overrides the language set for a Guest Collaborator.
If the people in a Step need the message in their own languages, leave that Step on Default content and set each guest’s language instead (see Changing Guest Collaborator Language). Use a custom message when the wording matters more than the language.