Email template inheritance in Aspera on Cloud
The Aspera on Cloud email template inheritance scheme accelerates and simplifies email customization.
There are two types of inheritance that interact with each other in the AoC email template customization schema:
- Inheritance from the base template
- Inheritance from parent template to child template (applies to base templates and to event-driven templates)
Base template inheritance
At each of the three template levels (organization, workspace, and shared inbox) you can configure a base template. The base template allows you to customize the fields that are common to all event-driven templates. You can customize the following fields only by configuring them at the base template:
- Subject prefix (for example, if you configure this field to read 'Urgent: ', the Subject line of each notification generated will begin with 'Urgent: ', followed by the subject entered by the sender)
- From
- Email logo (supported file types:.jpg,.png; maximum size: 512 kb; recommended dimension: square; see Customize your organization URL, name, and logo )
- Email title
- Footer
In addition to the base template for the organization, each workspace in the organization has its own base template. Further, each shared inbox in each workspace has its own base template.
Base templates influence related templates in two ways simultaneously:
- Settings in the base template propagate to event-driven templates at the same level.
- Settings from parent base templates are inherited by child base templates.
Propagation of settings from base templates to event-driven templates
The settings you configure for base template fields propagate to all the event-driven templates at that level. For example, when you customize the 'Subject-prefix' field in the base template at the organization level, that customized 'Subject-prefix' setting propagates to all the email templates at the organization level (for example, the 'Welcome to Aspera on Cloud' notification, the 'Package Received' notification, the 'Folder Shared' notification, etc.).
Similarly, settings you configure at the workspace base template propagate to all workspace-level event-driven templates. And settings from a shared inbox base template propagate to all shared inbox event-driven templates.
Inheritance from parent base template to child base template
Settings configured in the parent base template are inherited by the child base template: from organization base template to the base template in each workspace; and from workspace base template to the base template in each shared inbox in each workspace.
If you configure only the organization base template, those settings will:
- Be inherited by child base templates in workspaces and shared inbox
- Propagate through all event-driven templates in the organization.
However, each workspace has its own base template that you can customize to override the inheritance from the organization base template. If you do not override the settings inherited from the organization base template, the workspace templates display the settings configured at the organization base template.
Similarly, these workspace base template settings are inherited by each shared inbox base template (and in turn by the event-driven templates at the shared inbox level). Again, for each shared inbox, you can override the settings inherited from the workspace base template and configure customized shared inbox base template settings; again, the settings you configure at the shared inbox base template propagate to all the event-driven templates for that shared inbox.
Parent-to-child inheritance
For both base templates and event-driven templates, templates at each level inherit the configuration of templates at the parent level: shared inbox templates inherit from workspace templates; workspace templates inherit from organization templates.
However, you can override the inheritance for many configurable fields.
If you don't configure the templates at the workspace level, workspace-level notifications reflect the settings at the organization level. Similarly, if you don't configure the templates at the shared inbox level, shared inbox-level notifications reflect the settings at the workspace level (which may in fact inherit from the organization).
At any level, you can configure none, some, or all configurable fields. A configurable field that you don't configure inherits the configuration from the parent level.
Unique templates for internal and external users
If desired, you can configure unique templates for external users. External users are not members of your AoC organization, but when allowed by the AoC administrator, members of a given workspace can send to, share with, and request files from these external members.
For external user templates, both base and event-driven templates follow a parallel inheritance path to member templates. External user templates do not inherit from member templates.