Skip to main content
Design and CMS tool connections store a personal access token on the workspace. The Canva app, Figma plugin, and Sanity Studio plugin authenticate with OAuth access tokens (and Figma localhost connection tokens for development). Effective access is the token’s scopes intersected with your membership, role, and project access.

​
Canva

Follow the step-by-step guide: Localize Canva. Create a Canva connection with a token. In the Canva app, pick a native project, collect one JSON file per page, then apply existing translations to the selected pages.

​
Figma

Follow the step-by-step guide: Localize Figma. Create a Figma connection with a token. In the plugin, pick a native project, Upload source JSON (no job), Translate when you want a job, and Apply one locale at a time. Apply uses stored source stamps (figma.k.*); missing strings reset to source instead of leaving a previous language on the canvas. Plugin installation depends on how it is distributed to your team. If you do not have the plugin, contact support for availability and installation guidance.

​
Sanity Studio

Follow the step-by-step guide: Localize Sanity Studio documents. Create a Sanity Studio plugin connection with a token. In the Studio Hyperlocalise editor view or bulk tool, pick a native project, then choose target locales from that project’s configured list (sourceLocale and targetLocales from project languages). Upload (locale), Translate, and Write version operate on those tags only. OAuth grants are scoped to the Studio origin where the editor signed in. Batch import and Content editor Push to Sanity use the separate Sanity automation connection. See Localize Sanity documents (automation).

​
Resolve access or job failures

Check the selected workspace/project, token scopes, account role, and job status. If you lost a one-time secret, replace it rather than expecting to reveal it again. Revoke old credentials when replacing a connection. See Connection troubleshooting.