User Guide
Resident Translator translates Confluence pages into 27 languages without your content leaving Atlassian. The app runs entirely on Atlassian's platform (Runs on Atlassian) and uses language models hosted by Atlassian. The translation is created as a child page; the original page is never changed.
Translate a page
- Open the page and click ••• (More actions) in the top-right corner.
- Choose Apps → Translate page.
- Pick the target language and click Translate.
Short pages take a few seconds; long pages take a few minutes. You can close the window: the translation continues in the background, and when you open the window again it picks up where it is. The result is a child page titled Original title (LANGUAGE), for example Freigabe-Checkliste (DE).
Update a translation
Translate the page again into the same language. The existing translated page is updated rather than duplicated. Its title is updated too, unless someone has renamed it, in which case the new name is kept. The app only ever updates pages it created itself; it never overwrites other pages.
What is translated and what is not
| Translated | Never changed |
|---|---|
| Text, headings, tables, lists, task text, panel and expand titles, link labels | Code blocks, macros without visible text (for example Jira issues, table of contents), link targets, attachments, mentions, task status, terms on your "never translate" list |
Links to headings on the same page are updated to point to the translated headings. If a part of a page cannot be translated without risking the page structure, it is kept in the original language and the app tells you how many sections this affected.
Glossaries and "never translate" lists
- Site glossary (all plans): Confluence administration → Resident Translator. Only Confluence administrators can save it.
- Space glossary (Advanced): Space settings → Resident Translator. Only space administrators can save it. It extends the site glossary and wins where they overlap.
Format: one entry per line. "Never translate" takes one term per line. The glossary takes term => translation; you can also paste two columns from a spreadsheet. Lines starting with # are ignored.
deployment => Bereitstellung
rollback => Rücksetzung
incident => Störfall
Glossary terms are applied in the right grammatical form, so a term may appear inflected or as part of a compound word. "Never translate" terms are always kept exactly as written.
Plans and allowances
Allowances are measured in pages of text. One page of text is 1,800 characters, the translation-industry standard page; a Confluence page is often several pages of text. Code blocks and other content that is not translated do not count.
| Plan | Monthly allowance |
|---|---|
| Standard | About 28 pages of text per user, at least about 275 pages of text per site |
| Advanced | About 110 pages of text per user, at least about 1,100 pages of text per site; a choice between Fast and Best quality (Best uses four times the allowance); space glossaries; an extra onboarding allowance of two months' worth during the first 60 days |
| Free trial (30 days) | About 275 pages of text in total |
If the remaining allowance does not cover a whole page, the app translates the first sections that fit and shows them as a preview in the window, without saving anything to Confluence. After you upgrade or when the allowance renews, translate the page again into the same language: the translation continues from where it stopped, and the part already translated is not charged again. This works as long as the page and the glossary have not changed in the meantime.
Speed
Atlassian limits how fast language models can be used per site. In practice a site can translate roughly 4 million characters per hour. Translating a large space for the first time can take a day or more; everyday use is not affected.
Security and privacy
- No data leaves Atlassian; the app makes no calls to external servers.
- The app reads and creates pages with the permissions of the person using it.
- Translation data is deleted automatically after 7 days.
Details: see the privacy policy.
Support
Email support@skrd.dev on business days. Please include the page link, the target language and what you expected to happen.