One or more email recipients for a template can be configured in an email recipients’ grid on the email options tab of the content template form. The configurations will be populated into the to, cc or bcc parties of an email when it is generated for a template. Configurations options for recipients are as listed and shown in the screenshot below

• Current User Context – the user creating the email will be set as the recipient party
• User or Queue – an explicitly selected user or queue will be set as the recipient party. The user or queue is made available for selection once this picklist option is selected
• Party Path – a token is defined as the recipient party. This option uses the same token types as content tokens and will generally be a field token to load the recipient from the source record context. The value resolved by the token should be an emailable entity, for example a contact, account or user record
• Party Email Path – a token defines a path to a string column with the email address for a recipient party. This option uses the same token types as content tokens and will generally be a field token to load the recipient from the source record context. The value resolved by the token should be a string column in an emailable entity, for example a contact, account or user record

Example tokens for the party path recipient options are provided below

Party Path

Primarycontactid – on template sourced from account this would send to the primary contact

customerid|account.primarycontactid – on template sourced from case set recipient to the primary contact of the customer, where the customer is an account

Party Email Path

primarycontactid.emailaddress2 – on template sourced from account set recipient to the primary contact, but rather than using their primary email, use their secondary email address in the field with logical name

customerid|account.primarycontactid.emailaddress2 – on template sourced from case set recipient to the primary contact of the cases customer where it is an account, but rather than using their primary email, use their secondary email address in the field with logical name emailaddress2