login | sign up

Your session has timed out due to inactivity.

You can go back to the overview without login or use the login form to login again before redirect

Knowledge Base / one2edit™ v4 Admins – Essential Workshops / Set up a Template

Workshop 3: Create a Template – Quick Reference

Created on 13th March 2026 at 17:38 by Jamie O'Connell



This lesson covers the creation of a Template.

What is a Template?

A core element of one2edit™ is a Job, where a user is assigned to translate (or edit) a document via a workflow.

In one2edit™, a Template refers to a template of a job. The Template links a pre-prepared source-language document with one or more pre-defined workflows.

When a Template is started, it automatically:

  • creates a target-language version document from the defined source-language document.
  • applies a defined workflow to that version document.
  • starts the workflow, thus creating a job.

This is used as a controlled method of enabling users to start their own jobs without giving those users administrator privileges.

These kinds of "on demand" jobs are often used for the localization of marketing material by dealers or franchises (e.g. updating logos, addresses, etc.), as well as material such as business cards, seminar flyers, etc.

NOTE: Please ensure that you have prepared a project on the system. This would have involved linking the document as a one2edit™ project, and then creating and populating at least one Content Group within that document. Please also ensure that you have created and saved at least one workflow. This would have involved creating a workflow, and saving it as a template workflow.

Step 1: New Template

  1. Click the + (plus) button to create a new Template.
  2. Name: Give the template a name.
  3. Tags: You may add search tags to your Template, if required.
  4. Description: It may be useful to add a short description of this Template. This will be visible to those that can use the Template.
  5. Default Version: Every time someone starts a job from this Template, a version document will be created. The value you select here will define the Version text for those new documents. The + (plus) menu to the right is used to insert variable attributes into this text.
  6. Default Description: As with the Default Version field, the default Description of the generated version documents is defined here. The + (plus) menu to the right is used to insert variable attributes into this text.
  7. Template-Starter Options:
    • Allow template-starter to change default values: If this box is checked, a user who starts a job from this Template can edit the default Version and Description values for their job. If this box is not checked, the Version and Description values will be set to the values in the fields above.
    • Allow template-starter to use finished versions as source: If this box is checked, a user who starts a job from this Template can choose one of their own previously-completed jobs (if one exists) as the starting point for their new job. Only those jobs on which the user has worked in the past will be available to them (i.e. jobs that appear in the user's Job Archive). If this box is not checked, a copy of the original document will always be used for a new job.
  8. Document: Clicking on the [No document] button opens a dialog for choosing the source-language document to use with this Template. It is possible to change the selected document to another by clicking on this same area.
  9. Mode: There are two modes for a Template:
    • Create Version: This is the default mode. If this mode is selected, this Template will create a target-language version within the chosen project (i.e. the project chosen in the Document field above).
    • Duplicate Document: If this mode is selected, starting a job from this Template will spawn a duplicate project instead. This is not suitable for translation jobs, but can be useful for other kinds of self-service jobs.

Step 2: Add Workflows

  1. Select the Workflows tab.
  2. Click the + (plus) button to open the workflow-selection dialog, where you can choose the workflows for this Template.

NOTE: You can also drag-and-drop workflows into this dialog from the Workflows area.

  1. Your chosen workflows are displayed in the list.
  2. Click Save/Apply to create your new Template.

NOTE: Click the trashcan icon beside a workflow to remove it from the Template.

Step 3: Auto-assign Workflows to Specific Users

If you wish to automatically assign specific workflows to specific users who start jobs from this Template, you must:

  1. Uncheck the boxes next to all workflows.
  2. Select an unchecked workflow.
  3. Drag-and-drop users or user groups into the lower pane of the Template Details dialog to assign them to the selected workflow.

Now, when a user starts a job from this Template, they will be automatically assigned their workflow.

NOTE: If a user is assigned to more than one unchecked workflow, they will be offered a choice of which one to use.

NOTE: If there is a mix of checked and unchecked workflows, a user will be offered a choice between any unchecked workflows assigned to them, and any checked workflows.

NOTE: Multiple users and/or user groups can be assigned to a single workflow.

Step 4: Template Created

Your new Template has been created.

Any users that you assigned to a workflow in the Template will now be able to see it and start a job by clicking the Start button.

Step 5: Start a Job

  1. Click Start to start a job from your Template. You may need to take further steps in a Start Template dialog (see below).
  2. Once the job starts, you will be automatically brought to your Jobs list, where your new job will be displayed.
  3. If there is any pre-translation action in your workflow, you may see some items have been marked as light green, which means that they are Done, but not yet committed to review.

NOTE: If the pre-translation action is set to automatically commit items to review, and if your translation-memory database contains matches for all segments in the document, then the Translation step will be fully completed and will not appear in your Jobs list.

NOTE: If your user is not assigned to the first step of the workflow (i.e. the Edit/Translation step), then the job may also not appear in your Jobs list at this point. However, your view will still automatically change from Templates to Jobs.

NOTE: Start Template Dialog

  1. When a user clicks Start on a Template, they may see the Start Template dialog.
  2. This dialog guides the user through any steps they need to complete before the job is started.
    • Details: The user can change details about the job. Granted via the option: Allow template-starter to change default values.
    • Workflow: The user must select the workflow to use with their job. Shown if multiple checkmarked workflows are assigned to the Template.
    • Archive: The user may select a previously-completed job as their starting point. Granted via the option: Allow template-starter to use finished versions as source.

Once these steps are completed, the job will start, and your view will change to your Jobs list.

NOTE: If the user does not have any previously-completed jobs in their Job Archive, the Archive step will not be shown, even if the option is selected in the Template.

NOTE: If no workflows in the Template have the checkbox checked, then the Workflow step will not be shown.

NOTE: Template Access for Non-Admin Users

A user can access a Template if that user (or their user group):

  • has been assigned to a workflow in the Template's Workflow tab (see above).
  • has Template Admin privileges.
  • has been granted access to the folder containing the Template (see below).

To grant folder-access permissions to users:

  1. Double-click the folder, and choose the Permissions tab in the Folder Details dialog.
  2. Drag-and-drop user groups into the top part of the dialog. The Users and Groups dialog can be opened via the + (plus) button or via the main navigation menu.
  3. Select each user group to reveal their privileges in the lower part of the dialog.
  4. Check the box next to each privilege you wish to grant the users in that group.

In this example, we have granted read access, but not write access, meaning that these users can access the Templates in this folder and start jobs from them, but cannot edit/delete the Templates themselves.

NOTE: Users who are granted read access to a Template folder will be able to access all Templates in that folder. This is in contrast to users that have been assigned to Template workflows, and can only access those Templates to which they have been explicitly assigned.

NOTE: Folder-access privileges must be added at the user-group level, and cannot be granted to individual users.




© 2009-2026 1io BRANDGUARDIAN GmbH · All rights Reserved · Legal / Privacy Policy


top