# Organizations, factories and products

Source: https://docs.tai.ga/start/organizations-factories-products/

Taiga has three levels, and most things you configure live at one of them:

```
Organization
  └── Factory
        └── Product
```

An organization contains factories.
A factory contains products.
A product has one repository.
The work happens in products;
the levels above exist so that decisions made once do not have to be repeated.

That one-to-one rule is what decides how to model a larger system.
A system built from several services, each in its own repository, is not one product.
It is a factory, with a product per service.

## What belongs at each level

The useful question is not "where does this setting live" but "how widely should this apply".

| Level            | What lives there                                                                                             |
| ---------------- | ------------------------------------------------------------------------------------------------------------ |
| **Organization** | Policies, the approved tech stack, the design system, organization-wide instructions and knowledge, members. |
| **Factory**      | A knowledge base, one instructions document, and members.                                                    |
| **Product**      | Everything specific to its codebase: the specification, documents, initiatives, instructions and knowledge.  |

The organization is where the weight sits.
It carries the house style every factory inherits,
which is why [setting it up](https://docs.tai.ga/start/set-up-your-organization/) matters more than its brevity suggests.
A factory is deliberately light:
enough to give its products shared context and to control who can reach them.
That is what makes it the right home for a multi-service system.
The services share a domain, a stack and a definition of done,
and the factory is where you write those down once instead of per repository.

## Inheritance

A product sees its own settings, its factory's, and the organization's.
A factory sees its own and the organization's.
Nothing flows upward or sideways: one factory's instructions never reach another factory's products.

This is why the same idea can exist at more than one level.
Instructions and knowledge are not duplicated between them, they accumulate.
Each level adds guidance for a narrower audience, and a product ends up reading all three.

## Moving a product between factories

A product belongs to one factory, but not permanently.
Organization owners and admins can move it, from the product's own settings.

Because members get access to a product through its factory,
moving one is a change to who can open it.
The new factory gains access and the old factory loses it,
unless someone is on both.
So before anything changes, the confirmation shows who:
the people who will lose access and the people who will gain it, by name,
and, among the people the move touches, who keeps it either way and why:
on both factories, direct access to the product, or an organization admin.

A move can be undone.
Moving the product back restores exactly the access it had.
The confirmation message offers it,
and the settings page can move the product back at any time.

The product's link changes with its factory.
Old links keep working: they redirect to the new one.

The product keeps everything that is its own:
its specification and documents, its initiatives, its instructions,
and the files anyone uploaded to it.
What changes is the layer above.
The product starts reading the new factory's instructions and knowledge,
and stops reading the old factory's,
which is the same inheritance described above rather than an exception to it.
The old factory's own documents stay where they are; they were never the product's.

A product cannot be moved while it is planning or building.
A run that began under one factory's instructions
and finished under another's would be grounded in two different sets of guidance,
with nothing in the result to say which part came from where.
When that is the case, the confirmation says what is running
and offers to stop the line and move in one step;
you start the line again from the new factory.

If some of the product's uploaded files could not be re-filed under the new factory,
the settings page lists them with the reason,
and each can be retried without moving the product again.

## Where to go next

- [Set up your organization](https://docs.tai.ga/start/set-up-your-organization/) for the choices made at the top level.
- [Your first product](https://docs.tai.ga/start/first-product/) for the work that happens at the bottom one.