> ## Documentation Index
> Fetch the complete documentation index at: https://hyperlocalise.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Release notes

> What's new in Hyperlocalise Platform, grouped by month, with links to the related help articles.

These notes cover Hyperlocalise Platform: translation, review, automations, language resources, integrations, and developer surfaces. Each month lists customer-visible changes and links to the guides that explain how to use them.

Hyperlocalise CLI version notes live in the [CLI changelog](/changelog).

Start with [Your first translation](/platform/getting-started) if you are new to the product. Use [Troubleshooting and support](/platform/help/overview) when a change does not match what you see in the workspace.

## 2026 October

1. **AsciiDoc files.** Native projects and the CLI now translate AsciiDoc documentation (`.adoc`, `.asciidoc`, `.asc`). Prose, headings, lists, tables, and admonitions are translated. Macros, attributes, comments, and verbatim blocks stay in place. Upload each included file on its own; `include::` directives are preserved and not resolved. See [Supported formats](/platform/file-formats) and [Translate AsciiDoc](/cli/reference/formats/asciidoc).
2. **Unreal Engine rich text in gettext PO.** Native projects and the CLI now treat Unreal Engine style tags in `.po` catalogs as placeholders. Translators see chips such as **UE#0** in the [Content Editor](/platform/cat) and keep the markup when they download the file. See [Supported formats](/platform/file-formats), the [gettext POT and PO tutorial](/platform/tutorials/gettext-pot-po), and [Unreal Engine rich text in gettext PO](/cli/reference/formats/gettext#unreal-engine-rich-text).
3. **Merge identical strings.** Exact source-text duplicates collapse into one Content Editor row so you translate them once. Copies that already disagree stay visible as **Different translations**. Turn the project default on from [project settings](/platform/projects/settings), or switch **View** → **Show strings** in the editor. See [Merge strings](/platform/translation/merge-strings) and [Review translations](/platform/cat).
4. **Markdown and MDX document editor.** `.md` and `.mdx` sources open in a document File view instead of a segment queue. Review the stored target document, then [download translations](/platform/translation/download). Capabilities differ from string catalogs; see [Supported formats](/platform/file-formats) and [Translate Markdown](/cli/reference/formats/markdown).
5. **Word documents in File view.** Native projects accept `.docx` uploads. Open File view to inspect formatting and save a translated document. Office files are not handled by automatic file translation jobs. See [Upload source files](/platform/projects/files) and [Supported formats](/platform/file-formats).
6. **PowerPoint in File view.** Native projects accept `.pptx` uploads with the same File view workflow as other Office files. See [Supported formats](/platform/file-formats).
7. **Translation QA.** Workspace QA scans use a configurable check policy. Findings appear inline on compact side-by-side rows, and the QA overview shows charts, alerts, and scan notifications. Failed scans stay diagnosable from the run. See [Improve translation quality](/platform/help/quality), [Resolve translation issues](/platform/translation/issues), and [`hyperlocalise validate`](/cli/commands/validate).
8. **CLI QA validation.** `hyperlocalise validate` runs the same 12-check policy as Cloud QA against one segment or a JSON batch. Point `--policy-file` at a custom policy, or use the built-in defaults. See [`validate`](/cli/commands/validate), [`check`](/cli/commands/check), and [CLI v1.13.1](/changelog/v1-13-1).
9. **Grouped glossary and translation-memory tables.** Glossaries and translation memories use concept- and locale-grouped tables so you can scan terms and segments faster. Import and export still use [TBX, CSV, and XLSX](/platform/glossary-import-export) and [TMX or CSV](/platform/translation-memory-import-export). See [Language resources](/platform/knowledge).
10. **Editable character limits.** Side-by-side review shows length checks on the current string. You can edit the character limit when the project supports it. Fix **Length** before you approve. See [Review translations](/platform/cat) and [Improve translation quality](/platform/help/quality).
11. **Download translated variants.** You can download translated variants of Office files, images, MP4, and Markdown when those target files exist. Use project **Download translations** for complete files, not the queue export. See [Download translated files](/platform/translation/download) and [Supported formats](/platform/file-formats).
12. **Glossary interchange history and Crowdin TBX locales.** Open **Import/export history** on a native glossary to follow queued TBX, CSV, and XLSX runs. Crowdin TBX language IDs such as `de` map to a matching configured locale such as `de-DE` when the mapping is unambiguous. See [Glossary import and export](/platform/glossary-import-export).
13. **Board priority filtering.** Filter Board items by priority when you need an owner for a translation decision. Include the file, key, locale, and decision in the issue. See [Resolve translation issues](/platform/translation/issues) and [Board](/platform/cat#board).
14. **Sectioned project settings.** [Project settings](/platform/projects/settings) save **General**, **Locales**, and **Translation & Content Editor behavior** per section. Check **Source connection** first: native projects and connected TMS projects expose different fields.
15. **New Request in the workspace sidebar.** One-off translation requests are available again from **Agents** → **New Request**. State the project, files, and locales. Recurring work still belongs in [automations](/platform/automation/create-automation). See [Start a translation](/platform/translation/start).
16. **INI files.** Native projects and the CLI now translate Windows-style `.ini` localization files. Sectioned keys flatten as `section.key`. Comments, quoting, and section order stay in place on writeback. See [Supported formats](/platform/file-formats) and [Translate INI](/cli/reference/formats/ini).
17. **Qt Linguist TS files.** Native projects and the CLI now translate Qt Linguist catalogs (`.ts`). Context, disambiguation comments, and numerus forms become separate keys. Obsolete and vanished messages are skipped. Platform treats `.ts` uploads as Qt Linguist; TypeScript locale modules stay on the CLI. See [Supported formats](/platform/file-formats), the [Qt Linguist tutorial](/platform/tutorials/qt-linguist), and [Translate Qt Linguist TS](/cli/reference/formats/qt-linguist).
18. **Intercom Help Center localisation.** Connect Intercom from **Integrations**, then use the **Translate Intercom Help Center articles** automation to import articles as markdown into a native project. **Push to Intercom** writes Intercom drafts. It does not publish. Project locales must match Help Center locale codes exactly. See [Localize Intercom Help Center articles](/platform/connections/intercom).
19. **HTML File view and tag-path keys.** Native `.html` / `.htm` files open in File view of the stored page and keep a key queue. Keys follow the tag path (`html.body.h1`, `html.p`, `html.p.strong`, `html.p.strong.2`). Inline tags are separate segments, not placeholder chips. `head`, `script`, `style`, and `pre` stay untranslated. Re-upload files that still show hashed keys. See [Supported formats](/platform/file-formats), [Review translations](/platform/cat), and [Translate HTML](/cli/reference/formats/html).
20. **Braze localisation.** Connect Braze from **Integrations** with a REST API key and REST cluster. **Translate Braze Email Templates** imports HTML and **Push to Braze** writes locale-suffixed library copies. **Translate Braze Campaigns & Canvas** imports tagged draft JSON maps and writes approved locales through the Translation API. Both templates appear under Popular and Marketing. Do not attach both skills on one automation. Neither push publishes. See [Localize Braze](/platform/connections/braze).
21. **Canva collect, generate, and add to design.** A Canva connection stores a token and a project. Jobs use that project's source and target locales. The app collects one JSON file per page, generates each language, and replaces text on the chosen Canva pages. The first language row is the source locale, so you can write collected copy back after applying a translation. Languages appear as **English (en-US)**. There is no separate Canva `en` / `es` list. See [Localize Canva](/platform/connections/canva).

## 2026 September

1. **Hosted MCP server.** Coding agents such as Claude Code, Codex, and Cursor connect to Hyperlocalise over MCP with OAuth. Open workspace **Overview** and use the **Connect your agent** card. Agents can list projects, files, translations, glossaries, jobs, and Board items. See [MCP server](/platform/mcp), [MCP tool reference](/platform/developers/mcp-tools), and [Developer integrations](/platform/developers/overview).
2. **Visual workflow nodes.** Visual workflows add **Sequence**, **Merge / Join**, durable **Wait**, **Retry**, and graph-derived **For each** membership, plus typed input and output ports. Test drafts in mock mode, then publish a version. See [Visual workflows](/platform/visual-workflows), [Build reliable branches and retries](/platform/guides/workflow-data-and-retries), and [Fix automation problems](/platform/help/automations).
3. **GitHub content sync.** Native projects can pull source files from a connected repository and push ready translations as a pull request. Sync does not generate translations; add a [source-upload automation](/platform/automation/create-automation) or [start a translation](/platform/translation/start) after the source arrives. See [Sync content with GitHub](/platform/automation/content-sync), [Connect GitHub](/platform/connections/github), and the [GitHub localization tutorial](/platform/tutorials/github-localisation-workflow).
4. **Lottie and dotLottie.** Platform accepts Lottie JSON and `.lottie` archives. Translation covers editable text layers and leaves shapes, timing, and images unchanged. See [Translate Lottie animation text](/cli/reference/formats/lottie) and [CLI v1.13.0](/changelog/v1-13-0).
5. **Glossary import, export, and run history.** Native glossaries import and export **TBX**, **CSV**, and **XLSX** asynchronously. **Import/export history** lists queued and completed runs, including replace-mode TBX backups. Filtered and mirrored exports are available from the glossary actions menu. See [Glossary import and export](/platform/glossary-import-export) and [Language resources](/platform/knowledge).
6. **Translation memory TMX and CSV interchange.** Create or update a workspace memory from **TMX** or **CSV**, including Crowdin-style locale-matrix CSV. Export all locales or one language pair. See [Translation memory import and export](/platform/translation-memory-import-export).
7. **Jobs grouped by status.** The project job list groups work by status and keeps filters in the URL. Open a job to retry, cancel, or mark it failed. See [Track and recover jobs](/platform/translation/jobs) and [Translation failures](/platform/help/translation-failures).
8. **Website domain research.** Link a hostname, verify ownership, pick research markets, then save keywords and track rankings. Research does not publish website copy. See [Website and market research](/platform/domains), [Verify a website domain](/platform/research/verify-domain), and [Research keywords and track rankings](/platform/research/keywords-and-ranks).
9. **GitLab repository context.** Administrators can connect GitLab from **Integrations**. Manual and scheduled automations can use **Use GitLab repo** for repository analysis. Merge-request comment tools and GitLab content sync are not part of this workflow. See [Connect your tools](/platform/integrations).
10. **Canva production connect.** Create a Canva connection with a [personal access token](/platform/settings#personal-access-tokens), default project, and locales, then paste the one-time connection token into the Hyperlocalise Canva app. See [Connect design tools](/platform/connections/design-tools).
11. **Native translation QA reports.** Workspace QA findings can be reviewed in a queue and promoted to Board items. Use **Has issues** in the Content Editor for string-level checks. See [Improve translation quality](/platform/help/quality) and [Resolve translation issues](/platform/translation/issues).
12. **Projects and Queries API.** A read-only API on `https://api.hyperlocalise.com/v1` lists your identity, accessible projects, and workspace Queries with a personal access token. File upload and job creation stay on `https://hyperlocalise.com/api/v1`. See [Choose an API](/platform/developers/api-overview), [Projects and Queries API](/platform/developers/projects-and-queries), and [Files and jobs](/platform/api).
13. **Framework and repository tutorials.** Platform docs now include end-to-end guides for [GitHub](/platform/tutorials/github-localisation-workflow), [React Intl and ICU](/platform/tutorials/react-intl-icu), [Vue i18n](/platform/tutorials/vue-i18n), [iOS strings](/platform/tutorials/ios-strings), [Android string resources](/platform/tutorials/android-string-resources), [gettext POT and PO](/platform/tutorials/gettext-pot-po), and [XLIFF](/platform/tutorials/xliff).
14. **Slack Connect support channel.** When workspace **Overview** offers a Slack Connect invitation, accept it to open a shared support channel. That invitation is separate from the Slack integration used by automations. See [Contact support](/platform/help/contact-support) and [Connect your tools](/platform/integrations).
15. **Role permission matrix.** **Members** → **Role permissions** shows what each workspace role can do. Invite teammates with a role and a team so project access stays scoped. See [Roles and permissions](/platform/workspace/roles) and [Invite teammates](/platform/workspace/members).
16. **Image and video File views.** Image File view extracts text layers for review. Video File view supports sound and on-screen text refinement for `.mp4` clips. See [Supported formats](/platform/file-formats) and [Review translations](/platform/cat).
17. **Board.** The Issues feature is now **Board**. Track product and terminology decisions there, and keep string-level placeholder or length problems in the Content Editor. See [Resolve translation issues](/platform/translation/issues).
18. **MCP translation and glossary tools.** Hosted MCP adds `list_files`, `list_translations`, `get_translation`, `update_translation`, `upload_sources`, `download_translations`, `run_workflow`, `list_jobs`, `get_job`, `get_project_status`, `query_glossary`, `create_glossary_concept`, `query_translation_memory`, and `get_knowledge_memory`. See [MCP tool reference](/platform/developers/mcp-tools).
19. **Ahrefs and Zernio in automations.** Connect Ahrefs or save a Zernio API key, then add the matching tool to an automation. Confirm the intended account before a run that publishes or changes external content. See [Connect your tools](/platform/integrations).
20. **Locale progress on project overview.** Native projects show per-locale translation progress on the overview so you can see coverage before opening the editor. See [Create a project](/platform/projects/create-project) and [Start a translation](/platform/translation/start).
21. **Custom spellcheck dictionaries.** `hl check` accepts per-locale Hunspell allow-lists through `spellcheck.dictionary_dir` or `--dictionary-dir`. See [`check`](/cli/commands/check) and [CLI v1.12.0](/changelog/v1-12-0).
22. **Import Board items from Excel.** You can import issues from `.xls` and `.xlsx` files when you need to bring an existing tracker into Board. See [Resolve translation issues](/platform/translation/issues).
23. **Cloud path aliases for CLI sync.** Optional `files[].cloud_path` keeps Platform file identity stable when local `from` / `to` paths move. See [Connect the CLI](/platform/cli), [sync push](/cli/commands/sync-push), and [CLI v1.13.0](/changelog/v1-13-0).

## 2026 August

1. **Personal access tokens.** Every active member can create a token that acts as that person in the workspace. Tokens inherit the owner's role and project access. Use them for the [Figma plugin](/platform/connections/design-tools), [Canva connections](/platform/integrations#canva), and local scripts. Coding agents still authenticate through [MCP OAuth](/platform/mcp), not PATs. See [Personal access tokens](/platform/settings#personal-access-tokens).
2. **Figma plugin.** Extract text from a Figma page, create translation jobs, and pull completed locales with a personal token. Review layout on the target page after apply. See [Connect design tools](/platform/connections/design-tools).
3. **Markdown and MDX as documents.** `.md` and `.mdx` files open as editable documents rather than key-value queues. See [Supported formats](/platform/file-formats).
4. **Standards-compliant TMX import and export.** Native translation memories import and export TMX 1.4 with validation reports. CSV remains available for spreadsheets. See [Translation memory import and export](/platform/translation-memory-import-export).
5. **Translation-memory explorer.** Search, filter, and paginate TM entries. Open an entry to inspect provenance and edit it when you have access. See [Language resources](/platform/knowledge).
6. **Concept-based glossaries.** Native glossaries store concept-linked source and target terms, including forbidden terms. Workspace, team, and project linking control who can edit. Provider glossaries stay read-only. See [Language resources](/platform/knowledge) and [Glossary import and export](/platform/glossary-import-export).
7. **Segment locks.** Lock a string in the Content Editor so a grouped save or automation does not overwrite it. Locked copies stay out of merge-string writes. See [Review translations](/platform/cat) and [Merge strings](/platform/translation/merge-strings).
8. **Maximum length on strings.** Set or import a character limit on native strings. The editor reports **Length** failures before approval. See [Review translations](/platform/cat) and [Improve translation quality](/platform/help/quality).
9. **Queue filters, sort, and filtered download.** Filter the queue by untranslated, needs review, approved, has issues, skipped, hidden, and unsaved translations. Sort untranslated first. Export the filtered view as CSV, TMX, XLIFF, or XLSX, up to 5,000 matching segments. See [Review translations](/platform/cat), [Download translated files](/platform/translation/download), and [Prepare a review handoff](/platform/guides/review-handoff).
10. **Hidden strings.** Hide strings from the default queue on native projects and supported Crowdin workflows. Bulk hide is available where the provider supports it. See [Review translations](/platform/cat).
11. **Subtitles.** Native projects accept `.srt` and `.vtt` files for file translation jobs and segment review. See [Supported formats](/platform/file-formats), [SRT](/cli/reference/formats/srt), and [WebVTT](/cli/reference/formats/webvtt).
12. **Image, video, and Office File views.** File view covers `.png`, `.jpg`, `.webp`, `.mp4`, `.docx`, `.xlsx`, and `.pptx`. Automatic file translation jobs do not cover Office files; upload or edit the translated file in File view. See [Supported formats](/platform/file-formats) and [Upload source files](/platform/projects/files).
13. **Source-upload automations from existing files.** A **Source upload** trigger can run against files already in the project, not only a new upload event. Test with a small file first. See [Create a translation automation](/platform/automation/create-automation) and [Update source content safely](/platform/guides/update-source-content).
14. **Human-readable Board IDs.** New issues use the project identifier as a prefix, such as `HL-12`. Change the identifier in [project settings](/platform/projects/settings); existing IDs keep their original prefix. See [Resolve translation issues](/platform/translation/issues).
15. **Issue inbox.** Workspace **Inbox** collects issue notifications. Open an item to the matching Board entry. See [Resolve translation issues](/platform/translation/issues) and [Contact support](/platform/help/contact-support).
16. **Create-job composer.** Native and provider projects share one create-job flow. Provider-backed jobs can still open in the connected TMS. See [Track and recover jobs](/platform/translation/jobs), [Start a translation](/platform/translation/start), and [TMS integrations](/platform/tms).
17. **Per-project guidelines.** Upload tone, audience, and product context on the project or the workspace. Supported files include Markdown, PDF, DOCX, PPTX, CSV, JSON, and TXT. See [Add translation guidelines](/platform/knowledge/guidelines).
18. **MCP Board tools.** Hosted MCP can list, create, and update Board items and comments (`list_issues`, `create_issue`, `get_issue`, `update_issue`, `list_issue_comments`). See [MCP tool reference](/platform/developers/mcp-tools).
19. **Translate-on-source-upload template.** Saved automations include a template that translates uploaded source content into the project's target locales and leaves output for review. See [Create a translation automation](/platform/automation/create-automation) and [Automate your work](/platform/automations).
20. **GitHub automation triggers.** GitHub push and pull-request-opened events can start a saved automation after you [connect GitHub](/platform/connections/github) and enable the repository. See [Create a translation automation](/platform/automation/create-automation) and [Fix automation problems](/platform/help/automations).
21. **Default translation memory for native projects.** New native projects receive a workspace translation memory so the Content Editor has a place to store approved pairs. See [Language resources](/platform/knowledge).
22. **MCP `list_issues`.** Agents can filter Board the same way the workspace list does, including status, type, priority, locale, assignee, and project. See [MCP tool reference](/platform/developers/mcp-tools).

## 2026 July

1. **All-files Content Editor.** Open **Content Editor** in the project sidebar to review every file in one queue instead of one file at a time. Filter and search still apply. See [Review translations](/platform/cat).
2. **Side-by-side review.** The editor shows source and target together, with save draft and approve on the current string. Share a segment link when a teammate needs that row. See [Review translations](/platform/cat) and [Roles and permissions](/platform/workspace/roles).
3. **Native and provider jobs.** Create, inspect, and delete translation jobs for native projects and connected Crowdin, Lokalise, or Phrase projects. Use **Open in provider** when the connected system owns the job. See [Track and recover jobs](/platform/translation/jobs) and [TMS integrations](/platform/tms).
4. **Crowdin, Lokalise, and Phrase in the Content Editor.** Connected projects browse provider files and write supported saves back to the provider. Smartling connections do not currently expose a Content Editor. See [TMS integrations](/platform/tms) and [Moving to Hyperlocalise](/platform/getting-started/moving-to-hyperlocalise).
5. **Public files and jobs API.** Upload sources, create jobs, poll status, and download reconstructed translations at `https://hyperlocalise.com/api/v1` with an organization API key. The CLI uses the same API for [Platform sync](/platform/cli). See [Files and jobs](/platform/api) and [Choose an API](/platform/developers/api-overview).
6. **MCP Server tool in automations.** Connect an external MCP server from **Integrations**, then add the **MCP Server** tool to an automation. To connect an agent *to* Platform, use the [hosted MCP server](/platform/mcp) instead. See [Connect your tools](/platform/integrations).
7. **Knowledge Memory.** Workspace and project **Guideline** pages store instructions that automations and the Content Editor can use. Updating a guideline does not rewrite existing translations. See [Language resources](/platform/knowledge) and [Add translation guidelines](/platform/knowledge/guidelines).
8. **Teams and member assignment.** Invite people from **Members**, choose a role, and add them to a team for project access. A workspace role without team access still cannot open a private project. See [Invite teammates](/platform/workspace/members), [Roles and permissions](/platform/workspace/roles), and [Project access](/platform/projects/access).
9. **File tree search and actions.** Search the project file tree and use context-menu actions to open, import, or download a path. Keep source paths stable across uploads. See [Upload source files](/platform/projects/files) and [Update source content safely](/platform/guides/update-source-content).
10. **Import and download on Files.** Restore **Import translations** and **Download translations** on the files page. Import writes approved targets for matching keys; download returns complete target files. See [Import existing translations](/platform/translation/import) and [Download translated files](/platform/translation/download).
11. **New Request in the chat dock.** One-off agent requests open as a dedicated conversation. Identify the project, files, and locales before confirming. See [Start a translation](/platform/translation/start).
12. **App language.** The workspace UI follows the language you select in the app shell. Product UI locale is separate from project source and target locales. See [Workspace administration](/platform/settings).
13. **Board comments and permanent URLs.** Issues support threaded comments with @mentions and stable URLs you can share. See [Resolve translation issues](/platform/translation/issues).
14. **Ahrefs and Semrush in automations.** Connect those accounts from **Integrations**, then add the matching tool to a saved automation. See [Connect your tools](/platform/integrations).
15. **Translate with agent.** Native project files expose **Translate with agent** so a scoped request can enqueue generation without leaving Files. Review the job, then open the Content Editor. See [Start a translation](/platform/translation/start) and [Your first translation](/platform/getting-started).
16. **TMS source upload through the public API.** The files API can send sources into a connected TMS project when that provider supports the path. See [Files and jobs](/platform/api) and [TMS integrations](/platform/tms).
17. **Chat dock repository context.** Select a GitHub repository so the agent can look up source usage while you review a string. Connecting GitHub still does not move files until you configure sync or an automation. See [Connect GitHub](/platform/connections/github) and [Review translations](/platform/cat).
18. **CSV import for Board.** Import tracker rows with a column-mapping wizard when you already have an issue list. See [Resolve translation issues](/platform/translation/issues).

## 2026 June

1. **Content Editor workspace.** Review source and target text, glossary and translation-memory suggestions, and AI recommendations in one editor. Generation and approval stay separate steps. See [Review translations](/platform/cat) and [Your first translation](/platform/getting-started).
2. **Crowdin, Phrase, and Lokalise connections.** Connect a supported TMS from **Integrations**, then open the provider's project in Platform. Capability boundaries differ by provider. See [TMS integrations](/platform/tms), [Connect your tools](/platform/integrations), and [Moving to Hyperlocalise](/platform/getting-started/moving-to-hyperlocalise).
3. **Teams.** Create teams, assign members, and use teams to grant project access. See [Invite teammates](/platform/workspace/members) and [Project access](/platform/projects/access).
4. **Billing and plan usage.** **Settings** → **Billing** shows plan usage, invoices, and plan changes. Only administrators can open the billing portal. See [Manage billing and usage](/platform/workspace/billing).
5. **Workspace knowledge.** Upload shared style and product context so automations and reviewers use the same instructions. See [Language resources](/platform/knowledge) and [Add translation guidelines](/platform/knowledge/guidelines).
6. **Canva design translation.** Upload design text, run a file translation job, and apply completed locales in the Hyperlocalise Canva app. Inspect layout after switching language. See [Connect design tools](/platform/connections/design-tools).
7. **GitHub repository context for automations.** After you connect GitHub and enable repositories, automations can use repository context. Refreshing the repo list does not upload sources. See [Connect GitHub](/platform/connections/github) and [Automate your work](/platform/automations).
8. **Glossary compliance.** The Content Editor warns on missing required terms and forbidden alternatives. Mark forbidden terms when you create glossary concepts. See [Language resources](/platform/knowledge) and [Improve translation quality](/platform/help/quality).
9. **Queue filters and share links.** Filter the queue and copy a link to a segment. See [Review translations](/platform/cat).
10. **Per-file translation import.** Import an existing target file against one native source path. Matching keys are marked approved. See [Import existing translations](/platform/translation/import).
11. **Native comments.** Add comments on native project strings in the Content Editor. Crowdin issue comments also appear for connected Crowdin projects. See [Review translations](/platform/cat).
12. **Job views.** Switch project jobs between row and kanban layouts. **My Jobs** splits work you created from work assigned to you. See [Track and recover jobs](/platform/translation/jobs).
13. **Contentful webhook trigger.** Saved automations can start from a Contentful entry create or update event. A webhook trigger does not by itself sync Contentful files. See [Create a translation automation](/platform/automation/create-automation).
14. **Trust Center.** Security and compliance documents are available from the Trust Center linked in the docs footer. See [Contact support](/platform/help/contact-support) if you need a specific control mapped to a workflow.
15. **Translate-on-upload for native projects.** Uploading a source file can start a matching automation when you configure a **Source upload** trigger. Uploading alone still does not translate. See [Upload source files](/platform/projects/files) and [Create a translation automation](/platform/automation/create-automation).
16. **Lokalise and Phrase OAuth.** Complete the provider authorization flow, then verify the intended account and project before you review strings. See [TMS integrations](/platform/tms) and [Connection troubleshooting](/platform/help/connections).
17. **Native project workflow.** Native projects store source files and translations in Platform: create the project, upload files, request translation, review, and download. See [Create a project](/platform/projects/create-project), [Translation workflows](/platform/translation/workflows), and [Getting started for managers](/platform/getting-started/managers).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.