People variables
This section describes the variables for staff (guides/employees) linked to a booking or activity. Because multiple people can be linked, these variables live inside a loop: place them between <!-- BEGIN people --> and <!-- END people -->. The loop repeats once per linked person.
The steering variable {S_PEOPLE} indicates whether any staff is linked (true/false) and can be used to show the table only when staff is present.
| Variable | Description | Example |
|---|---|---|
| {people.RESOURCE_TYPE} | Name of the staff group (resource type) | Gidsen |
| {people.REMARK} | Remark on this person's link to the booking/activity | Ochtenddienst |
| {people.INITIALS} | Initials | J. |
| {people.PREFIX} | Name infix (prefix) | van |
| {people.LASTNAME} | Last name | Jansen |
| {people.SEX} | Sex | M |
| {people.NUMBER} | Staff number | 1042 |
| {people.NOTES} | Internal notes on the person | Rijbewijs B |
| {people.EXPERIENCE} | Experience (free text) | 5 jaar rondleidingen |
| {people.EDUCATION} | Education (free text) | Gidsopleiding 2019 |
| {people.IBAN} | IBAN account number | NL00BANK0123456789 |
| {people.NAME} | Full composed name | J. van Jansen |
| {people.USERNAME} | Username of the linked user | jjansen |
| {people.EMAIL} | Email of the linked user | jansen@example.com |
Example: a table that shows one row per linked staff member.
<table align="center" border="1" cellpadding="0" cellspacing="1" style="width:100%">
<tbody>
<tr>
<td>Type</td>
<td>Naam</td>
<td>E-mail</td>
</tr>
<!-- BEGIN people -->
<tr>
<td>{people.RESOURCE_TYPE}</td>
<td>{people.NAME}</td>
<td>{people.EMAIL}</td>
</tr>
<!-- END people -->
</tbody>
</table>
The addressed person: {PERSON_*}
In an email addressed to one scheduled person — the six staff notifications and manually emailing staff — that single recipient is available separately as standalone {PERSON_*} variables. Use {PERSON_FULLNAME} for the salutation. Unlike the people loop, which contains all linked people, {PERSON_*} refers to the addressed person.
| Variable | Description | Example |
|---|---|---|
| {PERSON_RESOURCE_TYPE} | Name of the staff group (resource type) | Gidsen |
| {PERSON_REMARK} | Remark on this person's link to the booking/activity | Ochtenddienst |
| {PERSON_INITIALS} | Initials | J. |
| {PERSON_PREFIX} | Name infix (prefix) | van |
| {PERSON_LASTNAME} | Last name | Jansen |
| {PERSON_SEX} | Sex | M |
| {PERSON_NUMBER} | Staff number | 1042 |
| {PERSON_NOTES} | Internal notes on the person | Rijbewijs B |
| {PERSON_EXPERIENCE} | Experience (free text) | 5 jaar rondleidingen |
| {PERSON_EDUCATION} | Education (free text) | Gidsopleiding 2019 |
| {PERSON_IBAN} | IBAN account number | NL00BANK0123456789 |
| {PERSON_NAME} | Full composed name | J. van Jansen |
| {PERSON_USERNAME} | Username of the linked user | jjansen |
| {PERSON_EMAIL} | Email of the linked user | jansen@example.com |
| {PERSON_FULLNAME} | Salutation-ready full name of the addressed person | J. van Jansen |
Note: {FULLNAME} is the customer of the booking — not the addressed person. For the person, use {PERSON_FULLNAME}. A worked example is available under this explanation for administrators.





