> ## 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.

# Frequently Asked Questions

> Common questions about accounts, translating, workflow, and the API.

## General

**What is TextSetu?**
A translation management platform — one shared workspace for managing all the text
in your product across every language. See the [Introduction](/docs/introduction).

**Who is it for?**
Localization managers, translators, reviewers, and developers. See
[Introduction → Who it's for](/docs/introduction#who-its-for).

**How is it different from a spreadsheet?**
Structured keys (so syntax never breaks), an approval workflow, glossary and TM
suggestions, quality checks, full history/rollback, branching, and 40+ file
formats for import/export — none of which a spreadsheet gives you.

***

## Accounts & access

**How do I sign in?**
With email & password, or via Google, GitHub, GitLab, or Bitbucket SSO. See
[Getting Started](/docs/getting-started).

**I was invited but can't find the invitation.**
Check the invitation email, or sign in and look for the **Pending Invitations**
banner shown at the top of the app (and on the onboarding screen).

**Can one person be in multiple organizations?**
Yes. Use the org switcher in the top navigation to move between them.

**Can someone have more than one role?**
Yes — TextSetu supports multiple roles per person at the org, project, and team
level. Effective permissions are the union of all roles. See
[Roles & Permissions](/docs/guides/roles-and-permissions).

**Who can approve translations?**
Org Owner, Org Admin, Project Admin, and Project Approver. See the
[Approval Workflow](/docs/guides/approval-workflow).

***

## Translating

**What do the cell colors/states mean?**
Empty (untranslated), Draft, Pending review, Approved, or Outdated. See
[Translating → Cell states](/docs/guides/translating#cell-states-at-a-glance).

**Why was my edit saved as "pending review" instead of published?**
The project has **Approval required** on and you're not an approver, so your edit
became a proposal awaiting review. See the
[Approval Workflow](/docs/guides/approval-workflow).

**What does "outdated" mean?**
The source text changed after this value was translated, so the translation may no
longer match. It's a signal to revisit it.

**How do plurals work?**
A key can have separate plural forms (e.g. *one* / *other*), each translated on its
own, respecting each language's plural rules. See
[Translating → Plurals](/docs/guides/translating#plurals).

***

## Glossary & Translation Memory

**What's the difference between a glossary and translation memory?**
A glossary enforces *terminology* (individual terms, with rules and QA). TM reuses
*whole translations* (sentence-level fuzzy matches). See the comparison in
[Translation Memory](/docs/guides/translation-memory#tm-vs-glossary--whats-the-difference).

**Why am I seeing a "forbidden term" warning?**
A glossary attached to the project marks that term as forbidden — it usually
suggests the preferred alternative (e.g. use "Bag", not "Cart"). See
[Quality Checks](/docs/guides/quality-checks).

**Can one glossary/TM apply to several projects?**
Yes. Both are first-class objects with an "applicable projects" setting.

***

## AI translation

**Can TextSetu translate with AI?**
Yes. AI translations run through an org-scoped **AI engine** using Claude, GPT,
Gemini, or DeepSeek — per key or in bulk. See [AI Translation](/docs/guides/ai-translation).

**BYOK or credits — how do I pay?**
Two ways: **BYOK** (connect your own provider API key — free and unmetered), or
**TextSetu platform keys** (metered against a prepaid **credit** balance). Platform
runs are refused up front if you can't afford them, never stopped mid-run.

**Does AI respect my glossary and approval workflow?**
Yes. The glossary and translation memory are the highest-precedence layer, so they
override the model's own judgment. AI writes also follow approval: with approval
on they land as proposals (or an approver can apply directly), and protected main
branches are respected.

***

## Branches & history

**What are branches for?**
Working on translations in isolation (feature copy, big reworks) and merging back
into main, like Git. See [Branches](/docs/guides/branches).

**Can I undo a change?**
Yes — every value keeps full history; restore any prior version. See
[History & Rollback](/docs/guides/history-and-rollback).

**Who changed this string?**
The value's history records who changed it and when (and who approved it). Broader
actions are in the [activity log](/docs/guides/analytics-and-activity).

***

## Import & Export

**Which file formats are supported?**
40+ — JSON, XLIFF, CSV/Excel, Android XML, Apple `.strings`/`.xcstrings`, Gettext
PO, ARB, YAML, RESX, and many more. See [Supported File Formats](/docs/reference/file-formats).

**Will importing create duplicate keys?**
No — import merges by key. Matching keys are updated; only genuinely new keys are
created. See [Import & Export](/docs/guides/import-export).

**How do I move all languages at once?**
Use a multi-language CSV or Excel file.

***

Still stuck? Contact **[deeppatel234@gmail.com](mailto:deeppatel234@gmail.com)**.