Dashboard tour
Use the dashboard to turn an uploaded build into reviewed, published translations. Select the organization and project first; the work you see belongs to that scope.
Find the task you need
| Area | What to do there |
|---|---|
| Overview | See the current workflow and next action for the selected project. |
| Projects | Create a project and inspect its environments and release policy. |
| Integrations | Get framework setup instructions, project details, and runtime configuration. |
| Jobs | Inspect uploaded builds, estimate a translation run, and follow progress or failures. |
| Languages | Enable target locales, set fallback relationships, and manage versioned product terms. |
| Strings | Inspect the latest ready build's source text and target versions; search, filter, and edit translations. |
| Review | Resolve translations that need a human decision, individually or in a selection. |
| Releases | Publish a ready catalog and restore an earlier published version. |
| Usage | Compare committed usage, reservations, and limits; export usage. |
| Team | Inspect members and manage access when your role permits it. |
| Tokens | Create or revoke environment-scoped build credentials. |
| Settings | Manage organization settings and billing according to your role. |
AI agent setup delegates repository changes to your coding agent. Dashboard tasks become available once that integration uploads a build.
Follow your first build
- Open Jobs and confirm that an uploaded build contains the expected strings.
- Enable a target locale in Languages.
- Choose Translate latest build in Jobs, review its estimate, and start the run.
- Check the wording in Strings and resolve decisions in Review.
- Open Releases when a complete catalog is ready. Confirm the target environment before publishing.
Read the states correctly
Missing means no usable translation exists for that string. Needs review means a person must decide. Accepted means a translation is ready to contribute to a catalog. Published means an environment serves a selected catalog version. An accepted count or an empty review queue does not prove that the app is serving the new wording.
Understand access
Viewers can read project data. Editors can edit, translate, review, and publish. Admins and owners can also manage members and tokens. Billing management belongs to the owner. If a write action is unavailable, ask your organization's owner to check your role in Team.
Find your project, builds, languages, strings, releases, and spending controls.
Last updated October 3, 2026
Did this page get you to a working result?