The following email templates are currently used by The Things Stack: Full Name Identifier Scope Additional fields Tenant Created tenant_created Sent to the initial user of a tenant when it is first created. InitialPassword Invitation invitation Sent when inviting new users to the network. InvitationToken, TTL API Key changed api_key_changed Sent when the rights of an API Key have been changed. Key, Rights, ConsoleURL API Key created api_key_created Send when an API Key has been created. Key, Rights, ConsoleURL Collaborator changed collaborator_changed Sent when the rights of a collaborator have been changed. Collaborator, ConsoleURL Password changed password_changed Sent when the the password of a user has been changed. Temporary password temporary_password Sent when a temporary password has been requested for an user. TemporaryPassword, TTL User Requested user_requested Sent to admins when a user is created and needs to be approved. ConsoleURL Email validation validate Sent when a user is added as a collaborator of an entity, in order to validate their email. ID, Token, TTL Entity State Changed entity_state_changed Sent when the approval state of an entity changed. State Note: In templates that have TTL, you can also call FormatTTL to format the TTL as “in XX hours” The following fields can be used inside all of the email templates:

Note: We recommend getting familiar with the html/template template format first. Template Components An email template override has three components: The subject file, which contains the subject of the email and is named <identifier>.subject.txt. The text contents file, which contains the contents of the email in text format and is named <identifier>.txt. The HTML contents file, which contains the contents of the email in HTML format and is named <identifier>.html. Creating the Overrides In order to override a template, one must provide all three files as part of the email templates repository and then provide them as part of the configuration.