Translator workflow
Primary translator URL: https://translator.kalima.digital
Kalima separates client project administration from translation operations. Clients typically configure the project in the dashboard, then route operational translation work through the translator experience.
What translators work on
- phrase-level translation tasks
- terminology-sensitive strings
- review comments and QA fixes
- document and asset-related delivery workflows where enabled
Typical client workflow
- Client admin sets up the project in the dashboard
- Project content becomes available to translators and reviewers
- Translators work inside a focused editor with context and terminology support
- Reviewers approve or request changes
- Client team ships updates with visible status tracking
Workflow features visible in the product
- focused editor
- terminology tools
- QA validations
- review workflow
Best practices for client teams
- Define the source locale and supported locales before translation starts
- Decide who approves translations before inviting outside contributors
- Use review states consistently instead of bypassing approval in side channels
- Treat QA warnings as release blockers when the strings affect runtime behavior or formatting
When to use the translator app versus the dashboard
Use the dashboard for project setup, keys, configuration, phrase management, pages, assets, and team administration. Use the translator app for the day-to-day translation and review flow.
Support
Need help shipping this integration?
If you hit a blocker, contact Kalima with your project key, target environment, and a short description of what failed.