> ## Documentation Index
> Fetch the complete documentation index at: https://docs.textsetu.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting Started

> From a brand-new account to your first translated key, in about ten minutes.

This guide walks you from a brand-new account to your first translated key. It
should take about ten minutes.

***

## 1. Create your account

You can sign up in two ways:

* **Email & password** — register with your email address. You'll receive a
  verification email; click the link to activate your account.
* **Single sign-on (SSO)** — sign in with **Google, GitHub, GitLab, or
  Bitbucket**. No separate password needed.

If a colleague invited you, you'll instead receive an **invitation email** —
follow [Accepting an invitation](#accepting-an-invitation) below.

## 2. Create or join an organization

An **organization** is your workspace — usually one per company. After your first
login, TextSetu sends you to **onboarding**:

* **No organization yet?** Create one. Give it a name (e.g. "Acme Inc"); a URL
  slug is generated for you. You become its **Owner**. New organizations have
  **Translation Memory** and **Glossary** enabled by default.
* **Have a pending invitation?** It appears here — accept it to join that
  organization with the role you were invited as.

You can belong to multiple organizations and switch between them with the org
switcher in the top navigation.

## 3. Create your first project

A **project** is a single product surface you want to translate — a website, a
mobile app, a marketing campaign, etc.

1. Open **Projects → New Project**.
2. Name the project and choose a **source language** (the language you author
   content in, e.g. English).
3. Decide whether to turn on **Approval required** (you can change this later —
   see the [Approval Workflow](/docs/guides/approval-workflow)).

## 4. Add your target languages

Open your project's **Languages** tab (under the **More** menu) and add the
languages you want to translate *into* (Spanish, French, German, Japanese…). Each
language you add becomes a new column in the translation grid.

## 5. Add translation keys

A **key** is a stable identifier for one piece of text (for example
`home.hero.headline`). Its **value** is the actual text, and there is one value
per language.

You can add keys two ways:

* **Manually** — open the **Translations** tab and click **Add key**. Give it a
  name and the source-language text.
* **By import** — if your app already has translation files, go to
  **Import** and upload them. TextSetu auto-detects the format and creates all
  the keys and values for you. See [Import & Export](/docs/guides/import-export).

## 6. Translate

Open the **Translations** tab to see the grid: one row per key, one column per
language. Click any cell to edit it inline. As you type, TextSetu offers:

* **Glossary suggestions** — approved terms for words in the source text.
* **Translation memory suggestions** — previously translated sentences that
  match (≥75%).
* **Quality warnings** — e.g. mismatched placeholders or forbidden terms.

See [Translating](/docs/guides/translating) for the full walkthrough.

## 7. Export the finished translations

When translations are ready, go to **Export**, pick your target format (JSON,
XLIFF, Android XML, `.strings`, PO, …) and language(s), and download. Plug the
files into your app, and you're localized.

***

## Accepting an invitation

If someone invited you to their organization:

1. Open the invitation email and click the link, **or** sign in and look for the
   **Pending Invitations** banner shown at the top of the app (and on the
   onboarding screen), where you can Accept or Decline.
2. **New users** set a password to create their account, then are added.
3. **Existing users** simply click **Accept**.

Accepting an org invitation activates *all* the access prepared for you in that
organization at once — including any project or team memberships.

***

## Next steps

* Learn the vocabulary in [Core Concepts](/docs/concepts).
* Understand who can do what in [Roles & Permissions](/docs/guides/roles-and-permissions).
* Set up consistent terminology with a [Glossary](/docs/guides/glossary).
* Speed up repeat work with [Translation Memory](/docs/guides/translation-memory).