--- title: "Crowdin integration for multilingual translation of knowledge base" slug: "crowdin" description: "Connect the Crowdin platform with your Document360 knowledge base to serve your global clientele in multiple languages; with a click of a button." tags: ["Extensions", "Crowdin", "Integrations"] updated: 2026-04-16T10:25:24Z published: 2026-04-16T10:25:24Z --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.document360.com/llms.txt > Use this file to discover all available pages before exploring further. # Crowdin **Crowdin** is a cloud-based localization management platform that streamlines the translation process, making it more efficient. By integrating **Crowdin** with Document360, you can automate and enhance the localization of your multilingual knowledge base, combining both machine and human translation to ensure quality and accuracy. **Prerequisite** Before starting the integration, ensure that you have an active **Crowdin** account. If you don't have one, sign up using valid credentials. --- ## Basic setup guide ### Creating a project in **Crowdin** To use the **Crowdin** platform as a translation partner with Document360 for content translation, ensure you are a registered user of **Crowdin** on an enterprise account. 1. Log in to your [Crowdin enterprise account](https://accounts.crowdin.com/workspace/choose?continue=%2Fenterprise) and go to your **Crowdin** workspace. 2. Click **Create Project** on the right of the screen to initiate the setup. 3. In the project field, enter the name of your project. > [!NOTE] > ** NOTE > > We recommend having project names be the same to make the **Push to****Crowdin** option work seamlessly in Document360. If you choose to have different names in Document360 and **Crowdin**, follow the below steps. > > 1. Create a project in Document360 and **Crowdin** with the same names. > 2. Enable the extension for **Crowdin** in Document360 by creating the **Crowdin** API key. The project name must be the same to validate the API key. Document360 will not allow the storage of invalid API keys. > 3. Now, you can choose to change the names. 1. Next, select the source language of your project. > [!NOTE] > ** NOTE > > Similar to the project address, the source language cannot be changed once submitted. 1. Select the target languages that are added to the versions in your project. 2. Choose a workflow that maps out the flow of content within your project. 3. Click **CREATE PROJECT**. ![2_Screenvideo-Creating_a_Project_in_crowdin.gif](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/2_Screenvideo-Creating_a_Project_in_crowdin.gif) ### Document360 integration with the **Crowdin** project To integrate Document360 with your **Crowdin** project follow the steps below. 1. Navigate to **Settings** (**) in the left navigation bar****in the Knowledge base portal. 2. In the left navigation pane, navigate to ****Knowledge base portal** > API Tokens**. 3. Click **Create API token** if this is the first token you are creating. 4. Enter the **Token name** in the field. 5. Select the options required in the **Allowed Method(s)** field (GET, POST, PUT, DELETE). 6. Click **Generate** and copy the generated API token. ![](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/Crowdin%20integration.gif) 7. Next, return to the **Crowdin** integration webpage. 8. Select the created **Crowdin** project, and you will be taken to the project dashboard. 9. On the dashboard side menu, go to **Integration.** 10. From the list of integration options available, select the **Document360** application. 11. Now, the application requires an API token from Document360. **Paste** the copied API token. 12. Click **Log in with Document360.** ![](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/1_ScreenShot-Crowdin.png) > [!NOTE] > ** NOTE > > Machine translations are enabled for each project on **Crowdin**, with **Crowdin****Translate** as the default translation engine. If you want to change the translation engines, it is required to configure them before the project members can use them. Some of the other translation engines supported by **Crowdin** are > > - MT Engine IDs > - Microsoft Translator > - Yandex Translate > - DeepL Translator > - Watson (IBM) Translator > - ModernMT > - Amazon Translate > - Google Translate > - Google Cloud AutoML Translation > > [Click here](https://support.crowdin.com/configuring-machine-translation-engines/#:~:text=By%20default%2C%20machine%20translations%20are,suggestions%20in%20the%20project%20settings.) to learn more about how to configure machine translation engines on **Crowdin**. ### Acquiring API token from **Crowdin** From your **Crowdin** workspace, select the **Crowdin** project configured with your Document360 knowledge base. 1. From the top right corner, click **Profile**>**Account settings**. 2. Select the **Access tokens**, and in the **Personal Access Tokens** section, click **New Token**. 3. Enter the **token name** and select **All scopes.** 4. Click **Create**. 5. Your access token has been created. **Copy** the generated token. ### Integrating with Document360 1. Navigate to ****Connections**** (**) > **Extensions** in the left navigation bar****in the Knowledge base portal. 2. Under the **Translation & Browser extension** tab, select **Crowdin**. 3. **Paste** the copied access token in the API key section. 4. Enter the organization name from your **Crowdin** account. 5. Click **Save**, and you are ready to go. ![](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/Crowdin%20token%20ID.gif) You can now use the **Push to****Crowdin** option from Document360. ### Feature Highlights #### Sync categories and articles to **Crowdin** for translation You can sync the types and articles from your Document360 project to **Crowdin** for translation in the **Crowdin** workspace. > [!NOTE] > ** NOTE > > To sync articles seamlessly between Document360 and **Crowdin** workspace, ensure the project name is the same. Log in to your **Crowdin** account and select the **Crowdin** project configured with your knowledge base. 1. On the dashboard side menu, navigate to **Integration**. 2. You can view the **Crowdin****project** and the Document360 project side-by-side. 3. On the Document360 side, you can view the categories and articles from your connected knowledge base. 4. You can search for articles using the search bar. 5. Select the categories and articles you'd like to sync with your **Crowdin** project for translation. 6. Click the **SYNC TO** option in the Document360 section. > [!NOTE] > ** NOTE > > Each article synced with the **Crowdin** project would have 2 files. > > 1. The article content file, mostly in markdown or HTML format. > 2. The article title file, which is a .txt file. ## Push to **Crowdin** from Document360 - After you've integrated your Document360 project with your **Crowdin** project and synced your categories and articles, you can directly use the **Push to****Crowdin** feature on Document360. - For instance, you have synched and translated your articles on your knowledge base using **Crowdin**. Later, you may make some changes or update the content of your article. Instead of visiting your **Crowdin** workspace, you can directly click on Push to **Crowdin** from your Document360 article editor. - Click on the **Crowdin****icon** on top of the article editor. You can find it next to the **See contributor** option. **Default language** In the dropdown **Crowdin****Sync** info, you can view the time of the **Last push to****Crowdin** and the **Push to****Crowdin** button. **Non-Default languages** - In the dropdown **Crowdin** Sync info, you can view the time of the Last translation sync from **Crowdin**, the time of the Last push to **Crowdin**, and the **Push to****Crowdin** button. - Click the **Push to****Crowdin** button, and the latest article content will be synched to your **Crowdin** project. > [!NOTE] > ** NOTE > > Only the categories and articles already synced with the **Crowdin** project would be able to use the 'Push to **Crowdin**' feature. #### **Timestamp feature** You can now view the timestamp of the translation actions performed on the specific article. - **Last translation sync from****Crowdin**: The timestamp of the recent translation and Push to Document360 action performed from the **Crowdin** platform. - **Last push to****Crowdin**: The timestamp of the recent Push to **Crowdin** action from the Document360 side ### Translating your connected Knowledge base articles - From your **Crowdin** platform, select the **Crowdin** project configured with your Document360 knowledge base. On the **Project home**, you can find details about your project. - You can view the current translation status, make sure any translations are ongoing, and you can also pause the translation. - Below is the **Home** tab; under the **Translation** section, you can see the list of target languages for your project. Also, you can find individual **progress indicators** adjacent to them. - If you click on any language, you will be taken to a page that shows a detailed view of the categories and articles pushed to **Crowdin** from Document360 for translation. - You can invite members from your team or any external agencies to collaborate on the **Crowdin** platform. They can directly edit or review the machine-translated content before pushing it back to the Document360 project. --- ### FAQ #### Does the Document360 subscription include translation service? No, the Document360 subscription does not include the **Crowdin** translation service. However, you can integrate Document360 with **Crowdin** for translation purposes. #### Can multiple team members use different Crowdin API keys for the same Document360 project? No. The **Crowdin** extension in Document360 is configured at the project level, which means a single **Crowdin** integration is shared across the entire project. All team members working in the same project use the same **Crowdin** extension settings, including the configured API key and organization details. It is currently not possible to assign separate **Crowdin** personal API keys for individual team accounts within the same project. Application Programming Interface - A set of defined rules and protocols that allows one software application to communicate with and request functionality from another. APIs are the backbone of modern integrations. When Document360 connects to Slack, Intercom, or Google Analytics, it does so through their APIs. Document360 also provides its own REST API, enabling teams to programmatically manage articles, categories, and reader accounts from external systems. ## Related - [Multilingual Knowledge base](/getting-started-with-multi-lingual-knowledge-base.md)