Configuration templates (in the "Templates" area) allow you to create configuration fragments that you can apply for all instances. All templates require a unique name. Most template types are lists that you can reference in the configuration of action trees. This enables you to complete the configuration faster and also provides a form of processing instructions for categorizing the instance. For example, the instruction could specify that only certain element classes are processed, which is why you create the list of selectable classes centrally as a configuration template. You could also use an instruction to exclude specific folders (or more generally: "containers"), regardless of whether they come up in the data source or not. A folder filter would then be used for this. As a general rule, you can create templates for action trees for data sources, entry points, container filters and classes.

To use message stubbing, you need to define a stubbing template using the corresponding action ("StubbingDef"). This template defines the content that is created when the message is stubbed. It is created in the template. It is necessary to distinguish between HTML and text format, as this will affect how the message is displayed after stubbing.

The most important template is for the keywording in the ELO repository. When configuring a new instance, there are two default templates, one for archived elements and one for path components of the filing paths. This template defines how the relevant keywording information is generated, such as the keywording form that is assigned and the index field entries.