Email tokens automatically populate information in an email once the email is triggered in the onboarding process. There are only a few tokens available for email templates, but you can add more tokens by creating custom tokens.
There are two steps involved in creating custom email tokens for email templates:
- Create a new document template with the name EMAIL_CUSTOM_TOKEN_MAPPING using Document Generation — Manage Document Template.
- Map the fields on the document template that represent the email tokens. This is done using Document Generation — Manage Document Template Mapping.
In these steps, you are creating a document template that contains a list of email tokens.
Document Template

The standard Template ID for a document template is EMAIL_CUSTOM_TOKEN_MAPPING. When you create a new template in Document Generation- Manage Document Template, ensure that the Template ID is EMAIL_CUSTOM_TOKEN_MAPPING.
Configure the Template Content with the tokens that you want to map. SuccessFactors recommends adding the prefix CT_ to avoid confusion between the standard email tokens and the custom tokens.
The example template will map the Department field.
For a complete list of the fields used in the Document Generation Template screen, see the SAP Help Document: Field Details for Document Template Screens.
Document Template Mapping

After creating the custom token template, you must map the custom tokens using Document Generation- Manage Document Template Mapping. After mapping the custom tokens, you can insert the custom tokens in the email template in Email Services.
The example mapping is for the Department field.
Consider the following:
- Only the tokens that are mapped in Document Generation- Manage Document Template Mapping will appear in the email template token list.
- Fields from custom MDF objects cannot be mapped to custom tokens.
- Custom tokens are not supported in Nudge email notifications.
- Custom tokens are not supported in templates with trigger (ONB) Suite mapping error.