The dashboard
Everything that isn't code happens in the Translation Manager at app.langsys.dev: reviewing what the model drafted, sharing translations between projects, and managing the organization, the keys and the bill. These walkthroughs are for whoever owns that work, whether or not they write the code.
Managing translations
The Translations page is a to-do list per language. Open a machine draft, correct it, and save: the badge changes from the model's name to yours, and with Update Memory on the correction is remembered for next time. AI Translate drafts a phrase on demand, and Auto-next moves the editor straight on to the next one in the queue.
Mark a phrase Never Translate to keep it as written in every language. Under Manage Access, invite a translator and limit them to the languages they work in. A saved correction is live in the app on the next fetch, with nothing deployed.
Translation memory
Translation memory belongs to the organization, so a new project starts with every translation its sibling projects already have: one entry per sentence per language. A corrected line arrives in the new project with its author's badge, and no model is called for it. Use Translation Memory sits on the project's Locales tab and is inherited from the organization by default.
One organization, many projects
Every project starts from its organization: default locales, AI Translator settings and billing. A project can customize any of them and switch back to inheriting later. Project Funding decides whether projects may draw on the organization's balance, and how much a month.
Usage & credits
There are two meters. API usage units count requests against your plan's monthly allowance. Credits pay for machine translation, which is priced per word per locale, and come as prepaid or free credits. Transfer credits from the account to a project, then set that project's monthly credit limit and auto recharge on its Billing tab. Every machine translation appears as a line in the project's transactions.
Plans & payments
The Subscription page shows the organization's plan, billing cycle, this month's usage and the billing address. Change Plan compares the plans side by side. Cards live under Payment Methods and can be shared with an organization or a project; addresses and invoices have their own pages, with invoices filterable by scope and type.
Notifications
The inbox is in the user menu, filtered by read and unread. In its settings, choose in-app, email or both for new phrases, invitations, and being added to a project or organization. A project can override the account defaults, for example to email you about new phrases in one project only.
Connect your AI assistant
Connect Claude Code, or any MCP client, to Langsys and ask about your projects in plain language. Your browser opens on an Authorize Access screen that lists what the connection can do; approve it and the assistant works with a token of its own, never your password. The connection appears among your sessions under the account's Security tab, and ending it there retires the token. The setup is in the MCP guide.
More dashboard walkthroughs
These sit on the concept pages they belong to.
- Adding a language A new target locale on a live project, priced before anything is spent.
- Catching up a language AI Translate Pending for one locale or the whole project.
- AI Translator settings Auto-translate, auto-detect and per-project overrides.
- Translating a content block A <Translate> region edited as one block.
- API keys in production Activity, pausing a key, and rotation.