XTM Portal 26.2

Log in to XTM Portal as an Administrator.

In the menu on the left of the screen, select the cog icon . The Settings tab screen is displayed.

In the Settings tab screen, select the GENERAL tab.

In the General settings tab screen, select the PROJECT LIST tab.

In the PROJECT LIST tab screen, adjust the required settings:

1. in the Access rules section:

   • Shared customer access:

     • off (default): users only see projects that they have created or that have been shared with them, in the Project list page. For details, see the Share with setting description in Configuring the Translation request page.

     • on: users by default see all projects for the customers that they have access to, created by all XTM Portal users.

       To grant users access to specific customers, select them in the Shared customers multiple selection field.

       You can also enable the Shared customer files setting. For details, see below.

   • Shared customers. This multiple selection field is only active if the Shared customer access toggle switch has been selected. Use it to grant users access to specific customers.

   • Shared customer files. This toggle switch is only active if the Shared customer access toggle switch has been selected. You can set it to:

     • off (default): users see all projects for the shared customers that they have access to. However, they can only download files for projects that they have created or have been shared with them, in the Project list page.

     • on: users see all projects for the shared customers that they have access to, created by all XTM Portal users. Also, they can download files for these projects.

2. in the Actions section:

   • Enable project deletion:

     • off (default): only users with the XTM Portal Administrator role can delete projects in the Project list page.

     • on: not only XTM Portal Administrators, but also project owners can delete projects, however only these that they have created.

   • Set naming-pattern for downloaded files text field. Use this field to set the file name pattern for all project files that can be downloaded from XTM Portal: target files, source files, and reference materials.

     If the field is blank, the default name pattern for all downloaded files is used: project_{{ id }}-{{ fileType }}_files. XTM Portal adds the file extension ZIP automatically.

     Example 1. : downloaded files named using the default name pattern

     For a project with ID 680601, the default file names will be as follows:

     • for the project target files: project_680601-target_files.zip.

     • for the project source files: project_680601-source_files.zip.

     • for the project reference files: project_680601-reference_files.zip.

     
     

     You can customize the file-naming pattern by using a Twig template. You can use the Twig Playground to test the pattern (called "template" in Twig) before saving it in XTM Portal. You can use the components listed and described in the table below, and add appropriate alphanumeric values to create your naming pattern. Ensure that you follow the naming pattern creation rules listed below.

     Important

     Rules for creating file-naming patterns:

     • Do not include the .zip file extension in your pattern. XTM Portal inserts it at the end of your pattern automatically.

     • Test date formatting and language lists in the Twig Playground to ensure that they match your needs.

     • Only letters, numbers, underscores, and hyphens are kept. Any other character types (such as spaces, full stops, and brackets) will be removed automatically. If the file name is blank after cleaning (removing the unsupported characters), XTM Portal uses the default name mentioned above.

     • Ensure that the clean file name (without unsupported characters) does not exceed 100 characters. If the file name is longer, XTM Portal uses the default name mentioned above.

     • If the naming pattern set in a Twig template cannot be rendered, XTM Portal uses the default name mentioned above. That can happen, for example, if you use incorrect components to create your naming pattern.

     Table 1. Components for the file naming pattern

     Component	Description	Example of the component value
     {{ id }}	An XTM Portal project ID. Numeric value.	680601
     {{ name }}	An XTM Portal project name. Alphanumeric value.	26-00019 - Pilot project for Portal review
     {{ customer }}	An XTM Cloud customer name. Alphanumeric value.	Customer 1
     {{ createDate }}	An XTM Portal project creation date. Numeric value.	2026-05-11T09:10:19+00:00
     {{ updateDate }}	The latest XTM Portal project update date. Alphanumeric value.	2026-05-11T09:10:19+00:00
     {{ fileType }}	A downloaded file's type. Valid values: target, source, or reference.	target
     {{ sourceLanguageCode }}	The source language code.	en_GB
     {{ targetLanguagesCodes }}	The target language codes.	["fr_FR", "de_DE"]
     {{ completionStatus }}	An XTM Portal project's completion status. Valid values: NOT_STARTED, IN_PROGRESS, or FINISHED.	Not Started
     {{ status }}	An XTM Portal project's status. Valid values: Not Started, In progress, or Finished.	In progress
     {{ analizeStatus }}	XTM Cloud project analysis status. Valid values: Not Started, In progress, or Finished.	FINISHED

     
     
   Example 2. 1: how to insert the project number and file type in the name of a downloaded file

   You place your in-house project numbers and project description in the project name field. However, for downloaded files, you only want to extract the in-house project number from the project name and add a file type, followed by the word "files" at the end. To do so, use the pattern below:

   project_{{ name | split(' ')[0] }}-{{ fileType }}_files

   For a project whose name is 26-00019 - Pilot project for Portal review, you will get this target file name: project_26-00019-target_files.zip.

   Open this example in Twig Playground.

   
   
   Example 3. 2: how to insert the project ID and source and target language names in the name of a downloaded file

   To insert the project ID, file type and source and target language names for downloaded files, use the pattern below:

   project_{{ id }}--{{ fileType }}--{{ sourceLanguageCode }}--{{ targetLanguagesCodes | join("-") }}

   For a project with ID 680601, whose source language is English (UK) and target languages are German (Germany) and French (France), you will get this reference file name: project_680601--reference--en_GB--de_DE-fr_FR.zip.

   Open this example in Twig Playground.

   
   
   Example 4. 3: how to customize the date format in the name of a downloaded file

   To insert the project ID, file type, and the date when your project was last updated, using this date format: YYYYMMDD, use the pattern below:

   project-{{ id }}--{{ fileType }}-{{ updateDate | date('Ymd') }}.

   For a project with ID 680601, that was last updated on May 26, 2026, you will get this source file name: project-680601-20260526.zip

   Open this example in Twig Playground.

   
   
   Example 5. 4: what happens if incorrect symbols are used in the name of a downloaded file

   Imagine that you want to insert the project ID, file type, and the project creation date, in the date format: DDMMYYYY in the names of downloaded files, but you use unsupported symbols to join these values. For example:

   project:{{ id }}({{ fileType }}){{ updateDate | date('dmY') }}.

   For a project with ID 680601, that was last updated on May 26, 2026, you will get this target file name: project680601target26052026.zip.

   For the list of supported symbols, see Rules for creating file-naming patterns.

   
   

Select the Save button in the top right-hand corner of the screen.