Email variables: reference and examples
01What is a variable for? #sec_aaa796f4
A variable reserves space in the template for information that will only be known at the time of sending: resource concerned, reviewer's name, deadline or reason for a decision. REVIEWIT replaces this tag with the value provided by the business event.
<title>Votre avis est attendu sur {ResourceName}</title>
<p>La réponse est attendue avant le {DueDate}.</p>The content of <title> becomes the subject of the email. Variables also work in the preheader, body and HTML attributes.
02The five syntax rules #sec_f4ae7b0c
- Use a single pair of braces: {ResourceName} .
- Respect the case: {ResourceName} and {resourcename} are different.
- Do not invent a variable from its French label.
- Use only the variables guaranteed for the selected event.
- Send a test and check that no {Variable} string remains visible.
Values are encoded before insertion: a name containing < or & cannot modify the HTML structure. However, a missing variable is not removed: it remains readable as is in the message.
03Resource and campaign #sec_920795bd
| Variable | Meaning | Example | Attention point |
|---|---|---|---|
| {ResourceName} | Name or reference of the resource | Finance Space or #123 | Do not assume it is always a readable name |
| {ResourceType} | Functional type of the resource | SharePoint | Present it as a category |
| {Solution} | Source solution | Microsoft 365 | May differ from the resource type |
| {CampaignId} | Technical campaign identifier | 1842 | This is not a title |
| {CampaignTitle} | Readable campaign title | Quarterly access review | To be preferred when available |
| {SizeFormatted} | Already formatted size | 2.4 GB | Do not make any conversion in the HTML |
04People and responsibilities #sec_a976ada6
| Variable | Meaning | Example |
|---|---|---|
| {OwnerName} | Owner or responsible concerned | Camille Martin |
| {ReviewerName} | Reviewer at the origin of the decision | Alex Bernard |
| {DelegatorName} | Person who delegates | Samira Diallo |
| {EscalatedByName} | Person who triggers escalation | Morgan Petit |
| {ReassignedByName} | Person who reassigns the request | Noah Robert |
| {RequesterName} | Author of a deletion request | Lina Moreau |
| {RequestedByName} | Author of a request for advice | Hugo Simon |
| {AnsweredByName} | Author of the response | Inès Laurent |
| {RedirectedByName} | Author of the redirection | Louis Michel |
| {NewRecipientName} | New recipient of a consultation | Émilie Garcia |
| {CancelledByName} | Author of a cancellation | Adam Roux |
| {RevokedBy} | Person or service that revokes access | Security Team |
| {DecidedBy} | Person who makes the decision | Nora Fournier |
05Dates and deadlines #sec_0071f336
| Variable | Meaning | Example |
|---|---|---|
| {DueDate} | Review deadline | 2026-09-15 |
| {AnswerDueDate} | Response deadline for a dispute | 09/15/2026 |
| {DaysToAnswer} | Number of days granted | 7 |
| {WithdrawnDate} | Date of withdrawal of the dispute | 08/31/2026 |
| {CancelledDate} | Date of cancellation of the request | 08/31/2026 |
| {ProcessedDate} | Date of processing of the deletion | 09/01/2026 |
Formats may differ depending on the event. The value is already formatted: do not attempt to transform it in the HTML.
06Decisions and free texts #sec_4d708521
| Variable | Meaning | Example |
|---|---|---|
| {Decision} | Decision made after escalation | Access removed |
| {NewDecision} | Decision applied after dispute | Conforms |
| {Reason} | Reason entered by a person | The role is no longer necessary |
| {Argument} | Argument of a dispute | This access remains required for closure |
| {Question} | Question addressed to the consulted | Is this access still necessary? |
| {Answer} | Answer provided to the requester | Yes, until the end of the project |
| {Comment} | Comment associated with a request | Deletion validated with the business |
| {ResolutionNote} | Note summarizing the resolution | Justification accepted after control |
Free texts should be presented in a citation or isolated block. Do not insert them in the middle of a sentence: their punctuation and content are unpredictable.
07Safe variables for review events #sec_26ebb516
| Event | Guaranteed variables |
|---|---|
| ReviewsAssigned | {ResourceName} {CampaignId} {DueDate} |
| ReviewReminder | {ResourceName} {CampaignId} {DueDate} |
| ReviewsExpired | {ResourceName} {CampaignId} {DueDate} |
| EscalationNotice | {ResourceName} {CampaignId} {DueDate} |
| EscalationReceived | {ResourceName} only |
| DelegationReceived | {ResourceName} {DelegatorName} {Reason} |
| RequestReassigned | {ResourceName} {ReassignedByName} {Reason} |
EscalationReceived has multiple paths. {EscalatedByName}, {Reason}, {CampaignId} and {DueDate} are only present in some cases: the default template must not depend on them.
08Safe variables for challenges #sec_168763f9
| Event | Guaranteed variables |
|---|---|
| ChallengeRaised | {ResourceName} {ResourceType} {Solution} {OwnerName} {Argument} {AnswerDueDate} {DaysToAnswer} |
| ChallengeAccepted | {ReviewerName} {NewDecision} {ResolutionNote} |
| ChallengeDeclined | {ReviewerName} {ResolutionNote} |
| ChallengeWithdrawn | {OwnerName} {WithdrawnDate} |
| EscalatedDecisionNotice | {ResourceName} {DecidedBy} {Decision} {CampaignTitle} {Reason} |
09Safe variables for deletions and accesses #sec_f74356e3
| Event | Guaranteed variables |
|---|---|
| DeletionRequested | {ResourceName} {ResourceType} {Solution} {RequesterName} {Reason} {Comment} {SizeFormatted} |
| DeletionCancelled | {ResourceName} {CancelledByName} {CancelledDate} |
| DeletionProcessed | {ResourceName} {ProcessedDate} |
| AccessRevokedNotice | {ResourceName} {RevokedBy} {Reason} {CampaignTitle} |
10Safe variables for consultations #sec_ae8e18fe
| Event | Guaranteed variables |
|---|---|
| AdviceRequestedNotice | {ResourceName} {RequestedByName} {Question} |
| AdviceReceivedNotice | {ResourceName} {AnsweredByName} {Answer} |
| AdviceRedirectedNotice | {ResourceName} {RedirectedByName} {NewRecipientName} |
11Dormant events #sec_f453ddcd
The following events are present in the catalog but are not yet automatically emitted:
- PendingReviewsDigest;
- ChallengeReminder;
- DecisionAmended;
- DeletionRejected;
- ExceptionExpiring;
- GracePeriodEntered.
Their template can be prepared and previewed. It should not be interpreted as proof that automatic communication is already active.
12Two unavailable variables #sec_ad0f2f57
{DeepLink} and {SettingsLink} exist in some historical templates, but no value is currently provided for them. Do not create a button or link that depends on them.
Some historical manual reminders also use {{ReviewerName}}. This double-brace syntax is not that of automatic notifications. The editor must flag it and ask you to revert to {ReviewerName}.
13Pre-publication check #sec_b3e3a4da
A template is ready when :
- its event is selected;
- each variable is guaranteed for this event;
- no double braces are present;
- free texts are isolated in appropriate blocks;
- the subject and body have been previewed;
- a real test does not show any unresolved variables.
The Subscription Manager editor applies this reference when writing: the palette proposes the authorized variables, provides an example, and inserts them at the cursor position. Unknown or unavailable variables block the save; contextual variables trigger a warning.