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

# Core Concepts

> The building blocks of TextSetu: organizations, projects, keys, values, glossary, and translation memory.

This page defines the building blocks of TextSetu. Understanding these makes
every other guide easier to follow. For a one-line glossary of every term, see
the [Glossary of Terms](/docs/reference/glossary-of-terms).

***

## The hierarchy

```
Organization
├── Projects ─────────── translation keys + values (the work)
├── Glossaries ───────── shared terminology
├── Translation Memories  reusable translated segments
└── Teams ────────────── groups of people, assignable to projects
```

## Organization

The top-level workspace, usually one per company. Everything — projects, members,
glossaries, translation memories, teams — lives inside an organization. You can
be a member of several organizations and switch between them.

Organizations can have optional features enabled, such as **Translation Memory**
and **Glossary** — both are **on by default** for new organizations, and can be
turned off in org settings (which permanently deletes all TM/glossary data).

## Project

A project is one product surface you localize — a website, an app, a campaign.
A project has:

* A **source language** (what you author in).
* One or more **target languages**.
* **Translation keys** and their **values**.
* Settings such as **Approval required** and a **key separator**.

## Translation key

A **key** is a stable, unique identifier for a single string, e.g.
`checkout.placeOrder`. Keys don't change when the wording changes — that's the
point. A key can also carry:

* **Tags** for grouping/filtering.
* A **description** giving translators context.
* **Screenshots** showing where the string appears in the UI.
* **Plural forms** (e.g. separate *one* / *other* variants).

The **key separator** (default `.`) is just the character used to display keys as
a nested tree.

## Translation value

A **value** is the actual text for one key in one language. Each key has up to one
value per language. A value carries a **status**:

| Status             | Meaning                                                        |
| ------------------ | -------------------------------------------------------------- |
| **Draft**          | Work in progress, not finished                                 |
| **Pending review** | A proposed change awaiting approval (only when approval is on) |
| **Approved**       | Reviewed and published                                         |

A value also records **who approved it** and **when**, and keeps a full
[history](/docs/guides/history-and-rollback).

A value can be flagged **outdated** when the source text changes after it was
translated, signalling that the translation needs to be revisited.

## Language

A language is a locale you translate into (e.g. `es`, `fr`, `de`, `ja`). The
**source language** is the one you author keys in; **target languages** are the
ones you translate into.

## Glossary

A shared list of **terms** with approved translations and rules — e.g. *do not
translate "Nike"*, *never use "Cart" (use "Bag")*. A glossary is attached to one
or more projects, and its terms surface as suggestions and
[QA checks](/docs/guides/quality-checks) while translating. See
[Glossary](/docs/guides/glossary).

## Translation Memory (TM)

A store of previously translated **segments** (source ↔ translation pairs). When
you translate a string whose source matches a stored segment, the TM suggests the
stored translation, so identical or near-identical sentences are translated once.
See [Translation Memory](/docs/guides/translation-memory).

## AI engine

An org-scoped, reusable configuration that every AI translation routes through —
which providers/models to use, the brand voice and per-language instructions to
follow, and which glossary and TM terminology to honor. Set it up once and the
per-key "Translate with AI" button, the bulk page, and the API all use it. See
[AI Translation](/docs/guides/ai-translation).

## Branch

An isolated copy of a project's translations where you can make changes without
affecting the main line — then **merge** them back, like a Git branch. Useful for
big reworks or feature-specific copy. See [Branches](/docs/guides/branches).

## Team

A named group of people. Assign a team to a project (or organization) to grant
everyone in it access at once — handy for, say, a "Localization Team."

## Member & roles

A **member** is a person who belongs to an organization, project, or team. Each
membership carries one or more **roles** (TextSetu supports multiple roles per
person), which determine what they can do. See
[Roles & Permissions](/docs/guides/roles-and-permissions).

## Member status

Memberships have a status:

| Status      | Meaning                      |
| ----------- | ---------------------------- |
| **Pending** | Invited but not yet accepted |
| **Active**  | Accepted and in use          |
| **Removed** | Revoked                      |

***

Next: [Roles & Permissions](/docs/guides/roles-and-permissions).