Document templates are managed in the Document Administration area of the product. This can be access via Launchpad > Open Document Admin > Document Templates

To create a new template, select the correct area in which you wish to create your template, e.g. Email / SMS / Document. Then configure the following elements - note that the options available will vary depending on the template type.
The template types are defined in Global features under Document Assembly - the following types are available out of the box.
Template Types
Use the Document Issued option for most Word templates. The table below shows commonly used types.
Template Type | Description |
---|---|
Document - Attendance Note | Used for legal attendance notes. |
Document - Bundle Separator | Used for separating sections in bundle configuration. |
Document Internal | Used to produce Word documents that will not be sent externally. |
Document Issued | Used to produce Word documents that can be issued out externally. |
Document - Multi-Party | A document that will be issued out to multiple parties e.g. a letter that will go to multiple participants in a legal case and the content will be varied for each party e.g. Dear Fred, Dear George. |
Email - HTML | Most common email format. An email written in markdown HTML. |
Email - Multi-Party | An email that will go to multiple parties and the content will be varied per party. |
Email - Notification - HTML | A produce email notification. |
SMS | A markdown SMS template. |
Configuration Options
The following options can be configured within templates.
Tag Browser
The tag browser allows you to see the document tags that can be used on this document. The tag browser takes the data context specified for the document and interrogates the configuration for that work item to determine what data is available in tags.
For more information on using document tags and the document tag browser, look here.
Details
Configuration | Description |
---|---|
Template Type | The type of template to be used e.g. Document - Issued. |
System Name | The unique system name for the template - you should build up a naming convention for the template names. |
Name | The name that will be visible in the application for the template - end users will see this. |
Description | A meaningful description of the template's use. |
Categories |
To add a new Category, type in the name of the Category and click on the 'Add option' text that appears: Entries presented in the "Prepare Document" menu in Sharedo are grouped by Category: ![]() |
Active | Indicates if the document is active or not. It is best to switch a template to inactive initially, as there may be documents in flight. |
Pinned | Determines whether the Document is also presented in the "Pinned" Category at the top left of the "Prepare Document" menu. i.e. it creates a shortcut to the document. |
Data Context
![]() |
The Data Context of a template indicates what the document is being written about. For example, is it being written a new Instruction or a specific matter type.
This selection has a number of consequences: The Data Composer Tags available for use within the document template are restricted to the type of work selected here. E.g. Litigation Tags are available only for Litigation documents. Further, the document will be available for use only within the selected type of work (and otherwise hidden). Various other properties, such as where the generated documents are placed (see below), are also defaulted according to the Data Context. |
Question Sets - Participant
Select neither option, or select To, or select both To and Regarding.
To: Select one or more Roles from the Role lookup that appears:
The Role(s) determine to whom the document (typically a letter) should be directed. If only one Role is selected, the details of the Participant in the selected Role will be automatically presented to the user when generating the document:
If there are multiple Roles, or there are multiple Participants assigned to the same Role, then a list of all the appropriate Participants will be presented and the user will be asked to select which Participant is the recipient.
If no Role is selected, then all the Participants are presented to the user.
Regarding: This determines to whom the document refers to and also acts as a phase guard – i.e. the document cannot be generated until a Regarding Participant is selected. Again, multiple roles can be selected.
Note that there is a dedicated Tag which can be added to documents which explicitly refers to the Regarding Participant. So, for example, a letter could be directed at a solicitors firm representing multiple defendants. The user selects which defendant this letter regards. The chosen defendant’s name then appears in the letter.
Question Sets - Additional
These are Document Questionnaires which appear on the Prepare Document blade and contain a series of questions which the user completes prior to generating the document. Once selected, they can be Previewed.
The order in which they are presented to the user can be varied by dragging and dropping the name up and down the list of selected Question Sets.
Note that the navigation bars detailed below will not appear until the Data Context has been selected.
Pack Contents
Configuration | Description |
---|---|
![]() |
ShareDo templates can generate multiple documents. Use this option to add a second (or subsequent) document to the template. Note the Mandatory toggle. This allows the user to exclude the document from the generation process if required. |
![]() |
Attachments are physical documents (Word, PDF files, etc.) that can be attached to the Document Template pack. These do not contain Tags and no data is inserted into them when generated. Typically, these documents may be guides to legal processes, pro-forma terms and conditions documents, or perhaps directions to court, or maps. When selecting files to upload / attach, note that attachments have their own dedicated folder, away from other documents. |
![]() |
Enclosures are placeholder documents containing instructions to the person delivering the document (typically the print room) regarding which pre-printed documents also need to be included. These are typically items such as pre-paid stamped addressed envelopes or brochures. Note that enclosures have their own repository in ShareDo, accessible via the left-hand panel. |
Repository | The repository defaults to Templates. |
Output title | The output title of the file. This is what the end-user sees. |
Output file name | The file name of the physical output file. |
Mandatory | Setting this on means the document is mandatory in the pack. If it is off, the user can deselect the document for the pack. |
Source |
This points to the underlying Word/template file in the document repository that will be used for this template. When adding a new template, you can click on the Note the buttons within the document repository that allow folders to be created so that documents can be organised and grouped properly. |
Allows a matching rule to be added to a specific template. This allows you to conditionally change the underlying Word document or template that is being used depending on the actual work item. For example, you may wish to change the content of a document based on the region in which the work type is based or change the content based on the work type. |
|
Open up the document management system e.g. SharePoint / iManage, to view the template repository. | |
Preview the document template. |
Output and Delivery
This section configures where the produced documents will be placed and the configuration for any delivery methods, for example, email.
Configuration | Description |
---|---|
DMS - Default Folder | The document repository folder on the context work item where the documents will be placed, e.g. correspondence. |
Work Type |
This is determined by the Data Context. For each type of work on which a document is generated, use the options described below to define where the resulting document should be placed. |
Output Repository / Path |
The document.output.selectedFolder Tag will pick up the output folder selected by the end-user when generating the document (and default to the DMS folder selected above). Also, tags can be used to define the name of the output folders. E.g. if your folders on your work type are prefixed with something like a matter ID in your underlying document repository, you can use this area to prefix the tag onto the folder name. E.g., context.externalreference- document.output.selectedFolder would create an output folder of |
Vary by Type |
Allows you to add in further work types to specialise the output folders. For example, if the Data Context selected was at a reasonably high level - such as Matter - then the document could be generated for every work type underneath this level. These options allow you to select the Output Folder for each work type. |
Generate PDF automatically |
These options determine whether the document(s) generated should be converted to PDF format and, if so, whether the original Word documents should be deleted so that only the PDF documents remain (to prevent duplication). The file name of the PDF copy can be set here. |
Delivery Channels |
How would you like this document sent out? Can the generated document(s) be sent by email, fax, post, etc.? This option is only available for some template types. Click Configure to set the configuration for each delivery type. |
|
NB: The email configuration here is only for when a document is produced and then sent out as an attachment on an email. ![]()
|
|
|
Refresh on delivery | At the point at which the document is issued, the tags selected here will be refreshed. |
Display
Document templates are displayed to end users in the prepare document menus throughout the application. This section of the configuration controls when and how the template is displayed to the user.
Configuration | Description |
---|---|
Display in Menus | Set to on if you want this template to appear in Prepare Document menus. If the template is only going to be triggered via workflow, then it may not need to appear in a menu to the end user. |
Overide default display context |
The data context of a template indicates what the document is being written about. For example, it is being written about an order, a legal matter, or a contract. It may be, however, that you want to trigger the document from an associated work item to the piece of work - for example, a telephone call on a service desk ticket or from a proceeding/hearing on a legal matter. |
Display Rules |
This allows you to use contextual matching rules to determine when the template appears. For example, you may have a letter associated with the sale of a freehold property. If the work type only involves a leasehold property, then you do not need to display the template. Matching rules are extremely powerful and will give you a large degree of flexibility in your template display. For more information on matching rules, look here. |
Enable legacy display rules |
This is a legacy setting, replaced by the Display Rule option above. Select the phases of the work item when the template will be displayed. |
Approvals
This area of configuration allows an approval process to be configured against the document template. When the user completes their drafting process, the approval process will be triggered, and the document will be blocked from sending until an approval is received. If an approval is rejected, then the document is returned to the drafting state and can be resent for approval once corrected.
Configuration | Description |
---|---|
Default Approval Model |
Allows you to select whether the document is always approved or select from pre-configured approval models. Learn how to set up approval models here. |
Except when the user has one of the following competencies |
Competencies are a powerful product feature which allows users or external parties to be assigned competencies. Users with different levels of expertise may produce documents and in some cases may require approval - however, they may also have the level of expertise and level of training to not require approval. List here any competencies a user may have that would mean that the approval process would not need to be triggered and an alternative approval process could be triggered (set to 'Approval - not required' if no approval is required). |
Document Actions
This configuration section allows you to specify actions that can occur associated with the preparation or sending of the document.
Configuration | Description |
---|---|
Create a document expectation |
Configure a document expectation to be created on your work type when the document is sent out. This will ensure the user follows up if no reply is received. Note: If you are using execution engine workflow plans to send the document, you may wish to configure the document expectation within your plan. Some notable properties:
|
Create Document Delivery |
A template can be configured with different delivery methods. This action allows you to specify that a delivery method is automatically created when a document reaches a certain phase. This will also allow the channel to automatically be sent if all the tags can be populated. This option facilitates the automatic sending of a document. |
Create Payment | Allows a payment to be triggered when a document is produced. |
Create Time Entry |
Allows a preconfigured time entry to be created when a user produces a document. Narrative: The narrative attribute allows you to configure a description for the time entry. You can use tags to describe the entry too. It shows up on a generated document's time entry blade like in the following image. ![]() |
Jump to phase |
The prepare document task for creating documents has a number of phases that are used to facilitate different scenarios for creating documents e.g., complete, issued etc. This option allows you to specify that a document will automatically jump to a specific phase to reduce user actions. |
Refresh Document | Refreshes the document and its tags at the selected phase. |