`
## Sender Display Name for Emails
You can use the **Admin** > **Configuration** > **Email Settings** page to modify the "display name" that appears in the **From** field for Vault-generated emails. This value is separate from the actual email address, which is not configurable. For example, the display name is "Veeva Vault" in the default "Veeva Vault vault-emails@veeva.com". You may want to modify this to show your company name, for example, "VeevaPharm PromoMats Vault".
To modify the display name, edit the **Email From Name** field. Note that you should not use the following characters within this field due to standard email restrictions: `"` `( )` `,` `:` `;` `<` `>` `@` `[` `]`
## Document Message Tokens {#document_message_tokens}
Tokens are special bits of text that are replaced at the time the message is used. You can use the following tokens within the email content for document messages:
### URLs
* ${docInfoUrl}: Doc Info page for related document
* ${notificationHome}: Notifications page
* ${taskHome}: **Home** > **My Tasks** page
### Task Information
* ${taskDecisionComments}: For the related workflow, all participant names, task names, verdicts, completion dates, and comments; requires additional setup in a notification step of a workflow
* ${taskInstructions}: Workflow start comments entered by the workflow owner
### Workflow Recipient Information
* ${recipientMobilePhone}: Message recipient's mobile phone number
* ${recipientOfficePhone}: Message recipient's office phone number
* ${recipientName}: Message recipient's full name
* ${recipientEmail}: Message recipient's email address
* ${recipientFirstName}: Message recipient's first name
* ${recipientLastName}: Message recipient's last name
* ${recipientTitle}: Message recipient's title
### Workflow Owner (Initiator) Information
* ${workflowInitiatorMobilePhone}: Workflow owner's mobile phone number
* ${workflowInitiatorOfficePhone}: Workflow owner's office phone number
* ${workflowInitiatorName}: Workflow owner's full name
* ${workflowInitiatorEmail}: Workflow owner's email address
* ${workflowInitiatorFirstName}: Workflow owner's first name
* ${workflowInitiatorLastName}: Workflow owner's last name
* ${workflowInitiatorTitle}: Workflow owner's title
### Sender Information
* ${senderFirstName}: First name of the document's Coordinator, or the workflow owner if the Coordinator is not defined
* ${senderLastName}: Last name of the document's Coordinator, or the workflow owner if the Coordinator is not defined
### Document Owner Information
* ${docOwnerMobilePhone}: Document owner's mobile phone number
* ${docOwnerOfficePhone}: Document owner's office phone number
* ${docOwnerName}: Document owner's full name
* ${docOwnerEmail}: Document owner's email address
* ${docOwnerFirstName}: Document owner's first name
* ${docOwnerLastName}: Document owner's last name
* ${docOwnerTitle}: Document owner's title
### Document Fields & Information
* ${docNumber}: Document number
* ${docType}: Document type
* ${docSubType}: Document subtype
* ${docProduct}: Product, as a space-separated list if multiple products are selected
* ${docMajor}: Major version number
* ${docMinor}: Minor version number
* ${docNameNoLink}: Document name, as plain text
* ${docName}: Document name, as a link to the document's Doc Info page
* ${docStatus}: Status/lifecycle state
* ${docTitle}: Title
* ${daysToExpire}: Number of days before the expiration date
* ${taskDueDate}: Workflow due date
* ${linkToAnnotation}: Link to a specific annotation; this token relates to the User Mentions functionality.
* ${noteComment}: Text from an annotation's _Comment_ field (email templates only); this token relates to the User Mentions functionality.
### Vault Loader Information {#vault-loader-tokens}
* ${vaultLoaderFileLink}: Link to access the input file
* ${vaultLoaderFileName}: Input file name
* ${vaultLoaderObjectType}: Entity type
* ${vaultLoaderActionType}: Action type
* ${vaultLoaderSettings}: Loader settings
* ${vaultLoaderWhereClause}: Where clauses applied on extract
* ${vaultLoaderStartTime}: Start time
* ${vaultLoaderDuration}: Total duration
* ${vaultLoaderRecordsPerSecond}: Number of records processed per second
* ${vaultLoaderNumSuccesses}: Number of successfully processed records
* ${vaultLoaderSuccessLink}: Link to access the success log file
* ${vaultLoaderNumFailures}: Number of records that failed to be processed
* ${vaultLoaderFailureLink}: Link to access the failure log file
* ${vaultLoaderFailureReason}: Reason for the failure
* ${vaultLoaderRecordMigrationMode}: Whether _Record Migration Mode_ was enabled
* ${vaultLoaderNoTriggers}: Whether _No Triggers_ was enabled for _Record Migration Mode_
* ${vaultLoaderDocumentMigrationMode}: Whether _Document Migration Mode_ was enabled
* ${vaultLoaderChangeObjectType}: Whether _Change Object Type_ was enabled
## Web Action Tokens
You can use the following tokens within the email content for web actions:
* ${Object.id}: Object record ID
* ${Session.id}: Session ID
* ${Vault.domain}: Vault domain
* ${Vault.id}: Vault ID
* ${User.id}: User's ID
* ${User.email__v}: User's email
* ${User.name__v}: User's username
## Object Message Tokens {#object-message-tokens}
You can use the following tokens within the email content for object messages:
* ${Object.name__v}: Object record name
* ${Object.status__v}: Object record status
* ${Object.state__v}: Object record state
* ${Object.[custom field name]__c}: Object record's custom field name to be used for object-specific messages. Use the `;richtext` modifier to display the content in rich text format.
* ${objectType}: Object type
* ${Object.welcome_email_subject__sys}: Email subject line (_Checklists only_)
* ${Object.welcome_notification_text__sys}: Notification text (_Checklists only_)
* ${Object.welcome_email_text__sys}: Email text (_Checklists only_)
* ${taskName}: Task name
* ${taskDueDate}: Task due date
* ${recipientName}: Task recipient name
* ${taskHome}: Link to the My Tasks page
* ${taskVerdicts}: Task verdicts
* ${taskComments}: Task comments
* ${taskInstructionsByInitiator}: Instructions provided by the workflow owner
* ${notificationMessage}: Notification message
* ${workflowLabel}: Label of the workflow
* ${multiDocDocumentsListLatestVersion}: Workflow documents for latest version, with link
* ${multiDocWorkflowLink}: Document workflow name, with link
* ${workflowTargetNoLink}: Non-linked document workflow name
* ${multiDocDocumentsList}: Linked list of documents in a workflow
* ${multiDocDocumentsListDocNumber}: Linked list of documents in a workflow with each document's document number preceding the document name
* ${workflowContentsLink}: Linked list of documents in a workflow
* ${workflowContentsNoLink}: Non-linked list of documents in a workflow
* ${workflowInitiatorEmail}: Workflow owneremail
* ${workflowInitiatorFirstName}: Workflow owner first name
* ${workflowInitiatorLastName}: Workflow owner last name
* ${workflowInitiatorMobilePhone}: Workflow owner mobile phone
* ${workflowInitiatorName}: Workflow owner name
* ${workflowInitiatorOfficePhone}: Workflow owner office phone
* ${workflowInitiatorTitle}: Workflow owner title
* ${workflowErrorMessage}: Workflow error message
* ${vaultName}: Name of user's Vault
* ${uiBaseExtUrl}: Base URL of user's Vault
## Summary Email Tokens {#summary-email-tokens}
You can use the following tokens within the summary notification template:
* ${vaultName}: Name of user's Vault
* ${currentDate}: Date when the summary email was sent
* ${category.name}: Notification category name
* ${category.viewAllLink}: Launches notifications page with all notifications related to that category. This page is available for only 30 days.
* ${notification.senderImage}: Sender's user profile image
* ${notification.content}: Content of the notification. Corresponds to the _Notification_ Text field of the notification template
* ${notification.date}: Date when the notification was generated
[1]: #tokens
[2]: #document-messages
[3]: #object-messages
[4]: #summary-email-tokens
[5]: #supported-html
[6]: #configuring-summary-emails