[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["# Enable post-editing requests\n\n| Starting on June 30, 2025, Translation Hub is officially deprecated and will no longer be supported. You can continue using Translation Hub until on June 30, 2026, when it will be shut down.\n\n\u003cbr /\u003e\n\nTranslation Hub post-editing lets you bring in your own translators to\nreview machine translated content. You use the Google Cloud console to invite\ntranslators and add them to post-editing groups. You can add translators to one\nor more projects.\n\nWhen you create a post-editing group, you assign it to one or more portals\n(advanced-tier portals only), and then portal users can submit post-editing\nrequests against that group.\n\nInvite translators\n------------------\n\n1. In the **Translation Hub** section of the Google Cloud console, go to the\n **Users** page.\n\n [Go to the\n Users page](https://console.cloud.google.com/translation-hub/users)\n2. Click **Invite user**.\n\n3. Select **Translator** and then click **Continue**.\n\n4. Select **Add manually** to invite one translator or **Bulk import via a CSV\n file** to invite multiple translators in a single request, and then click\n **Continue**.\n\n5. Specify user details:\n\n - To manually add one translator, specify the translator's email address,\n sign-in method, post-editing groups, and fluent language pairs. The\n sign-in method specifies whether translators sign in with an email and\n password or with their Google Account (such as a Google Workspace\n account).\n\n - To invite translators in bulk, provide a CSV file where each line\n specifies a translator's email address, sign-in method, associated\n post-editing groups (optional), and fluent language pairs. You can specify\n an existing file in Cloud Storage or upload a local file to\n Cloud Storage. In either case, Translation Hub requires\n Cloud Storage permissions. For more information, see [CSV file\n for inviting users in bulk](#csv).\n\n6. Click **Done**.\n\n On the **Users** page, you can the view status of each translator:\n `Registered` or `Invited`. Registered translators have signed in at least\n once.\n\n### CSV file for inviting translators in bulk\n\nTo add multiple translators in a single request, specify their information in a\nCSV file. Each line of the CSV file uses the following format that contains the\ntranslator's email address, sign-in method, post-editing group names, and\nfluent language pairs: \n\n \u003cvar translate=\"no\"\u003eEMAIL_ADDRESS\u003c/var\u003e,\u003cvar translate=\"no\"\u003eSIGN_IN_METHOD\u003c/var\u003e,\u003cvar translate=\"no\"\u003eGROUP_NAME_1\u003c/var\u003e;\u003cvar translate=\"no\"\u003eGROUP_NAME_2\u003c/var\u003e,\u003cvar translate=\"no\"\u003eLANGUAGE_CODE:LANGUAGE_CODE\u003c/var\u003e;\u003cvar translate=\"no\"\u003eLANGUAGE_CODE:LANGUAGE_CODE\u003c/var\u003e\n\nThe sign-in method can be `google` for Google Accounts or `email/password` for\nall other email addresses. The post-editing group names are listed on the\n**Post-editing** page in the Google Cloud console. Use a semicolon to\nassociate multiple groups or language pairs to a single translator.\n\nThe following example shows a sample CSV. Don't include a header row for column\nnames. \n\n amal@altostrat.com,google,groupname1;groupname2,en:es;zh:de\n charlie@altostrat.com,email/password,,zh:es\n hao@myownpersonaldomain.com,email/password,\n\nTranslation Hub has a limit on the number of rows and CSV file size. For\nmore information, see usage limits in [Quotas and limits](/translation-hub/docs/quotas).\n\n#### Add Cloud Storage permission to Translation Hub\n\nTranslation Hub reads your bulk-import CSV file from a\nCloud Storage bucket. Translation Hub doesn't inherently have\npermissions to access Cloud Storage. To allow access, grant the\nTranslation Hub service account the `Storage Admin` role, which allows\nTranslation Hub to upload and read CSV files from your\nCloud Storage buckets.\n\n1. Go to the **IAM** page.\n\n [Go to the IAM page](https://console.cloud.google.com/iam-admin/iam)\n2. From the list of principals, check to see if the\n `cloud-translation-hub@system.gserviceaccount.com` service account already\n exists with the `Storage Admin` role. If not, proceed to the next step. If\n the service account already exist, skip these steps.\n\n3. Click **Grant access**.\n\n4. For the **New principals** field, add\n `cloud-translation-hub@system.gserviceaccount.com` as a principal.\n\n5. Click **Select a role** and then select the **Storage Admin** role.\n\n The role grants permissions for Translation Hub to add and read\n files in Cloud Storage buckets. To see the exact set of\n permissions, see the [assigned permissions](https://console.cloud.google.com/iam-admin/roles/details/roles%3Cstorage.admin) in the\n Google Cloud console.\n6. Click **Save**.\n\nCreate post-editing groups\n--------------------------\n\nA post-editing group contains one or more translators. You assign post-editing\ngroups to portals rather than assigning individual translators to portals.\n\nWhen portal users request a post-edit, they can select any post-editing group\nthat's assigned to their portal. Translation Hub shows relevant\npost-editing groups that contain translators who have fluency with the source\nand target language of their translated documents.\n\nTo create a post-editing group, you must have at least one translator invited to\nyour Google Cloud project.\n\n1. In the **Translation Hub** section of the Google Cloud console, go to the\n **Post-editing** page.\n\n [Go to the Post-editing page](https://console.cloud.google.com/translation-hub/post-editing)\n2. Click the **Create post-editing group**.\n\n 1. Specify a name for the group.\n\n These names are visible to portal users when they request post-edits.\n 2. Select translators to add to the group and then click **OK**.\n\n 3. Click **Continue**.\n\n 4. Select the advanced-tier portals to assign this post-editing group to and\n then click **OK**.\n\n 5. Click **Done**.\n\n Creating the translator group might take a few minutes. After the group is\n created, it's listed on the **Post-editing** page. Portal users can now\n send post-editing requests to the post-editing group.\n\nCapture post-edited translations\n--------------------------------\n\nTo capture edits during post-editing, portal users must specify a read-write\ntranslation memory when submitting a translation request. If portal users don't\nselect a translation memory, they cannot select one later and no post-edits can\nbe saved. If a portal user selects a read-only translation memory, no post edits\ncan be saved; the translation memory is used only for matching translations.\n\nYou can set a default translation memory so that Translation Hub\nautomatically sets a translation memory when a portal user requests a\ntranslation. That way, the default translation memory is always associated with\na translation job unless a portal user explicitly removes it or chooses a\ndifferent one.\n\nFor more information, see [Save and reuse human-reviewed translations](/translation-hub/docs/admin-translation-memory).\n\nWhat's next\n-----------\n\n- Learn how portal users can [request post-edits](/translation-hub/docs/user-post-edit).\n- Learn how translators [edit documents](/translation-hub/docs/translator-edit).\n- Learn how to [set a translation memory to read only](/translation-hub/docs/admin-translation-memory-manage#read-only)."]]
