# General Translation Platform: Get started with the Dashboard
URL: https://generaltranslation.com/en-US/docs/platform/dashboard/get-started.mdx
Docs index: https://generaltranslation.com/llms.txt
Description: Run translation, context, and review workflows from the General Translation Dashboard.

The Dashboard is the web app for reviewing translations, guiding the AI with context and glossaries, and managing settings and API keys.

## Key workflows [#key-workflows]

- **Define context and key terms for translation:** use Context Groups to guide terminology and style across projects. (See [Defining context for translations](/docs/platform/dashboard/guides/defining-context-for-translations)).
- **Review and edit translations:** compare locales, make manual edits, and inspect version history. (See [Reviewing and editing translations](/docs/platform/dashboard/guides/reviewing-translations)).
- **Add annotations:** label entries, add notes, and discuss translation decisions with your team. (See [Adding annotations](/docs/platform/dashboard/guides/adding-annotations)).
- **Translate Google Drive content:** connect Google Drive and translate Google Docs or Google Slides from the Dashboard. (See the [Google Drive Quickstart](/docs/integrations/google-drive/quickstart)).
- **Automate the whole process:** see [Locadex](/docs/platform/locadex/quickstart) to automate localization setup and maintenance.
- **Get product help:** open **Ask AI** from any Dashboard page to ask questions, search the documentation, and find the right settings. (See [Using Ask AI](/docs/platform/dashboard/guides/using-ask-ai)).



## Configuration [#configuration]

- **Create API keys:** use **Project > API Keys** for a single project and **Organization > Developer > API Keys** for broader automation. (See [API keys](/docs/platform/dashboard/reference/api-keys)).
- **Manage team access:** invite members from **Organization > Settings > Members**. (See [Organization settings](/docs/platform/dashboard/reference/organization-settings) and [Roles and permissions](/docs/platform/dashboard/reference/roles-and-permissions)).
- **Connect external services:** manage Organization-level authorizations under **Organization > Connections**. Connect providers or link resources under **Project > Integrations**. (See [Organization settings](/docs/platform/dashboard/reference/organization-settings)).
- **Configure projects:** update the project name, source locale, CDN delivery, and AI Context from project settings. You can also copy the project ID there. (See [project settings](/docs/platform/dashboard/reference/project-settings)).
- **Send events to your backend:** use webhooks to receive signed translation events. (See [Webhooks](/docs/platform/dashboard/reference/webhooks)).
- **Manage billing:** use **Organization > Plans** to compare plans. Use **Organization > Settings > Billing** to buy prepaid credits, set up auto-reload, and review invoices. (See [Managing billing](/docs/platform/dashboard/guides/managing-billing)).
- **Export security activity:** use **Organization > Settings > Audit Logs** or **Enterprise > Settings > Audit Logs** to download events and deliver them to Amazon S3. (See [Managing audit logs](/docs/platform/dashboard/guides/managing-audit-logs)).



## Navigation [#navigation]

The Dashboard is organized into nested scopes: **Enterprise**, **Organization**, and **Project**. Most teams use Organizations and projects. Enterprise is a layer for larger teams managing multiple Organizations.

- **Enterprise** contains Organizations, members, billing, and **Settings** for **General**, **SSO / SCIM**, **Access**, and **Audit Logs** across multiple Organizations.
- **Organization** contains **Projects**, Platform Context, **Connections** for authorized external services, **Usage**, **Plans**, and **Locadex > Automations** and **Locadex > Integrations**. **Developer** contains **API Keys**, **Webhooks**, and **Webhook Events**. **Settings** contains **General**, **Members**, **Access**, **SSO / SCIM**, **Billing**, and **Audit Logs**.
- **Project** contains **Overview**, **Translations**, Platform Context, **API Keys**, **Settings**, **Automations**, and **Integrations > Connected** and **Integrations > Catalog**.

Use the switcher in the header to move between scopes. The sidebar changes based on the selected scope.

If you do not see a page, check that you are in the right Organization or project and that your role has access.

**Ask AI** remains in the header next to search as you move between Dashboard pages.

## FAQs [#faqs]

<Accordions className="faq-accordions">
  <Accordion title="What is General Translation?">
    General Translation (GT) is the full-stack localization platform to translate your app, docs, and content into any language. GT combines open-source i18n libraries, an AI-native translation platform, and the purpose-built localization agent Locadex. We build a complete understanding of your codebase and product context by connecting your code, content, and translations. So you can bring the best translations of your product to the whole world.
  </Accordion>
  <Accordion title="How do I get an API key?">
    Create a project, then open **Project > API Keys** or **Organization > Developer > API Keys**. Project keys are used for one project. Organization keys support custom permissions for broader automation. (See [API keys](/docs/platform/dashboard/reference/api-keys)).
  </Accordion>
  <Accordion title="Can I edit translations after they are generated?">
    Yes. Use the **Translations** page to review and edit generated translations. You can also use annotations to label entries, add notes, and discuss translations with your team. (See [Reviewing and editing translations](/docs/platform/dashboard/guides/reviewing-translations)).
  </Accordion>
  <Accordion title="What is context?">
    Context tells AI how to interpret and translate your product. It helps preserve brand and product names, resolve ambiguous words (like whether "cells" refers to rooms, phones, bacteria, or spreadsheets), and keep style consistent across your Organization and projects. GT applies context through Context Groups, which include a Glossary for terminology and Custom Prompts for tone and style. (See [Defining context for translations](/docs/platform/dashboard/guides/defining-context-for-translations)).
  </Accordion>
  <Accordion title="How do I share terminology across projects?">
    Create a Context Group at the Organization level with shared Glossary terms and Custom Prompts, then assign it to multiple projects. Changes to the group apply everywhere it is assigned. (See [Defining context for translations](/docs/platform/dashboard/guides/defining-context-for-translations)).
  </Accordion>
  <Accordion title="How do I update existing translations after changing the Glossary?">
    Select relevant terms and use Apply Glossary to update existing translations that contain selected Glossary terms. (See [Defining context for translations](/docs/platform/dashboard/guides/defining-context-for-translations)).
  </Accordion>
  <Accordion title="How do I regenerate translations?">
    For code and uploaded translation files, use the CLI or Locadex to run a new translation pass; the Dashboard's **Translations** page does not run full-file retranslation. Linked Google Drive files can be regenerated with **Force retranslation** from the [Google Drive integration](/docs/integrations/google-drive/guides/managing-translations#force).
  </Accordion>
  <Accordion title="How do I sync Dashboard edits back to GitHub?">
    Use Locadex to create pull requests for Dashboard changes, such as manual translation edits or Apply Glossary updates.
  </Accordion>
</Accordions>

## Next steps

- /docs/platform/dashboard/guides/reviewing-translations
- /docs/platform/dashboard/guides/defining-context-for-translations
- /docs/platform/dashboard/guides/using-ask-ai
- /docs/platform/dashboard/guides/managing-billing

## Sitemap

See the full [sitemap](https://generaltranslation.com/sitemap.md) for all pages.
