FTP requirements and preparation for Localization Hub – iLangL

The FTP connector lets Localization Hub exchange localization content with your organization through a standard FTP or FTPS server. The Workspace places source content ready for translation into a dedicated folder, collects completed translated files from another folder, and moves processed files to an archive folder after import.

Before connecting FTP to the Workspace in Localization Hub, make sure the FTP / FTPS server, user account, folder structure, and connection parameters are ready.

This article explains what needs to be prepared before you create the FTP connection and FTP Configuration in Localization Hub.

In this article, you will prepare:

an accessible FTP / FTPS server
a dedicated user account
a recommended folder structure on the FTP server
connection parameters for the FTP connection and FTP Configuration

Before you start

To prepare FTP for Localization Hub, make sure you have the required server access, folder structure, and configuration details before you begin.

Note: The actual steps for connecting FTP to the Workspace and creating FTP Configurations are covered in a separate article.

1. Accessible FTP / FTPS server

You need an FTP / FTPS server that is reachable from the internet over the standard FTP control port 21.

FTPS, or FTP over TLS, is supported and strongly recommended.

When Use SSL is enabled in Localization Hub, the FTP connector uses explicit FTPS, also known as AuthTLS. This means the connection is upgraded to TLS so credentials and content are encrypted in transit.

The server must also allow passive data mode, or PASV mode, which is used by most modern FTP clients.

Firewall requirements

Make sure your FTP / FTPS server and firewall allow:

FTP control connection on port 21
passive data mode
the passive data port range configured on your FTP / FTPS server

2. Dedicated user account

Create a dedicated FTP user account for the Workspace integration.

The account should have permission to list, create, read, upload, rename, and delete files and folders inside the localization root.

We recommend using an account created only for the Workspace integration and scoped to the root folder used for Localization Hub. This keeps localization traffic separated from other FTP activity on the same server and reduces the risk of access to unrelated files or folders.

Recommended: Scope the dedicated FTP account to the Localization Hub root folder whenever possible.

3. Recommended folder structure on the FTP server

A single FTP server can be shared by multiple Localization Hub workspaces, such as Staging, UAT, and Production, and by multiple services within each workspace, such as Translation and MachineTranslation.

To keep everything organized and prevent one workspace or service from interfering with another, we recommend a four-level folder hierarchy.

High-level structure

Root folder / Workspace folder / Service folder / Operational folders

Example:

<ftp-root>/
  localization-hub/                        Level 1: shared root for all Localization Hub activity
    AcmeStore_Staging/                     Level 2: workspace folder
      Translation/                         Level 3: service folder
        Content for translation/           Level 4: operational folder
        Translations to deliver/           Level 4: operational folder
        Delivered/                         Level 4: operational folder
      MachineTranslation/                  Level 3: second service folder
        Content for translation/
        Translations to deliver/
        Delivered/
        Delivery with errors/
    AcmeStore_UAT/
      Translation/
        Content for translation/
        Translations to deliver/
        Delivered/
        Delivery with errors/
    AcmeStore_Production/
      Translation/
        Content for translation/
        Translations to deliver/
        Delivered/
        Delivery with errors/
      MachineTranslation/
        Content for translation/
        Translations to deliver/
        Delivered/
        Delivery with errors/

A complete path may look like this:

/localization-hub/AcmeStore_Production/Translation/Content for translation/

4. Folder levels explained

Level 1 — Root folder

Create one root folder on the FTP server dedicated to Localization Hub.

Example:

/localization-hub

This folder is shared by all workspaces and services. It keeps localization traffic clearly separated from other FTP activity on the same server.

The dedicated FTP account should be scoped to this folder when possible.

Level 2 — Workspace / environment folder

Inside the root folder, create one sub-folder per Localization Hub workspace.

We recommend the naming pattern:

WorkspaceName_Environment

Examples:

AcmeStore_Staging
AcmeStore_UAT
AcmeStore_Production

Each workspace is isolated inside its own folder. This folder is selected as the Workspace folder when configuring the FTP connection in Localization Hub.

For example:

/localization-hub/AcmeStore_Production

Staging, UAT, and Production are independent Localization Hub workspaces. If content is tested in Staging first and promoted through UAT to Production, each environment should have its own workspace folder and its own separate translation cycle.

Level 3 — Service folder

Inside each workspace folder, create one sub-folder for each translation service you intend to use.

Typical service folders include:

Translation
MachineTranslation

Each service folder maps to a separate FTP Configuration in Localization Hub. When setting up a configuration, this folder is selected as the Service Folder.

This allows one workspace to run several different translation workflows in parallel, with each workflow writing to and reading from its own isolated area.

Important: Service folders must be created manually before creating the corresponding FTP Configuration in Localization Hub. The Workspace does not create Level 3 folders automatically.

Level 4 — Operational folders

The Workspace automatically creates four operational sub-folders inside each service folder the first time content is exported to that FTP Configuration.

You do not need to create these folders manually.

Created automatically: The Workspace creates Content for translation, Translations to deliver, Delivered, and Delivery with errors on first export.

Folder	Purpose
Content for translation	Outbound folder. Source files uploaded by the Workspace, ready for translation.
Translations to deliver	Inbound folder. Completed translated files should be placed here for the Workspace to collect.
Delivered	Archive folder. Files are moved here automatically once translations have been imported.
Delivery with errors	Error folder. Files that cannot be processed during delivery are moved here automatically. A detailed error file named `<original filename>.error.txt` is added to the same folder.

Do not rename or delete these folders after they are created.

5. Who creates what

Use the table below to confirm which folders must be created manually and which folders are created automatically by the Workspace.

Folder level	Created by	Notes
Level 1 — Root folder, for example `/localization-hub`	User	Created once on the FTP server. Shared by all workspaces and services.
Level 2 — Workspace folder, for example `AcmeStore_Production`	User	Created manually for each workspace. Named using the `WorkspaceName_Environment` pattern. Selected as the Workspace folder in the FTP connection settings.
Level 3 — Service folder, for example `Translation`	User	Created manually inside each workspace folder, one per service. Set as the Service Folder in the FTP Configuration. Each service folder requires its own separate FTP Configuration.
Level 4 — Operational folders, such as `Content for translation`, `Translations to deliver`, `Delivered`, and `Delivery with errors`	Workspace	Created automatically by the Workspace on first export. Do not rename or delete these folders.

6. Connection parameters to collect

Have the following values ready before connecting FTP to the Workspace in Localization Hub.

These values are used when creating the FTP connection and FTP Configuration. You do not need to share the user name or password with iLangL unless you want iLangL to configure the FTP connection on your behalf.

Configuration note: The Use SSL setting is selected in Localization Hub during FTP connection setup. Confirm whether this option should be enabled before creating the connection.

Parameter	Description
Server	Host name or IP address of the FTP server, for example `ftp.example.com`. An `ftp://` or `ftps://` prefix is accepted and stripped automatically.
User name	Dedicated FTP account user name.
Password	Dedicated FTP account password.
Use SSL	Determines whether explicit FTPS is used. Recommended for all internet-accessible servers. Confirm whether this option should be enabled in Localization Hub.
Workspace Folder	The workspace folder at Level 2, for example `/localization-hub/AcmeStore_Production`. Set once per FTP connection.
Service Folder	The service folder at Level 3, for example `Translation` or `MachineTranslation`. Set per FTP Configuration. One FTP Configuration is required per service folder.

Important: The connector connects on port 21 and, when Use SSL is enabled, upgrades the connection to TLS via explicit FTPS, also known as AuthTLS. Make sure your firewall allows port 21 and the passive data port range.

Summary

Before FTP can be connected to the Workspace in Localization Hub, make sure you have:

prepared the FTP / FTPS server
created a dedicated user account
set up the recommended folder structure
collected the required connection parameters

The root folder, workspace folders, and service folders are created manually on the FTP server. The operational folders are created automatically by the Workspace on first export: Content for translation, Translations to deliver, Delivered, and Delivery with errors.

After these requirements are in place, you can connect FTP to Localization Hub and create the required FTP Configurations.