Skip to content
TaigaTaiga Docs

Set up your organization

Four answers about your organization decide how every project in it is judged. This page explains what they are, so you settle them deliberately rather than accepting defaults you never read.

The four answers

Section titled “The four answers”
Answer What it means
Region Not a choice today. Taiga is currently offered in one country, so this is fixed until that changes.
Industry Every industry you operate in. All of them, not just the main one.
Stack The languages and frameworks you build with.
Cloud The clouds you deploy to. Not having decided is fine: Other covers on-premises, multi-cloud and deciding later.

Industry, stack and cloud each take several values, and each needs at least one.

What Taiga builds from them

Section titled “What Taiga builds from them”

Your policies and approved tech stack are built from these four answers.

The important consequence is on industry: each industry you select adds its regulatory controls. They combine as a union, so selecting two industries does not average them or pick the stricter one. It applies both. A company that is both fintech and healthcare gets both sets, and every specification, architecture and security assessment in the organization is written against the combination.

This is the field most worth getting right, and the easiest to under-answer. Naming only your primary industry produces documents that look complete and quietly omit a second set of controls.

The stack and cloud answers become your approved tech stack, which is the reference the agents plan against when they choose technologies.

You can change them later

Section titled “You can change them later”

Sensible defaults are filled in for you, and none of these answers is locked once set. Taiga proposes a set and asks you to confirm it rather than making you start from nothing.

Changing them later is normal, and worth doing as soon as an answer is wrong. Correcting an industry after a project exists does not retroactively rewrite documents or code that were already generated, so the sooner it is right, the less there is to regenerate.

Review what was generated

Section titled “Review what was generated”

The generated policies live under Governance in the organization’s navigation, alongside your Design System and Audit Log. Read them before your first project rather than after: they are the standard everything is checked against, and they are much easier to correct while no work depends on them.

Your design system shapes output too

Section titled “Your design system shapes output too”

The four answers above decide what is allowed. Your design standards decide what generated interfaces look like, and they are read from Discovery onward, not only when an initiative is planned in detail.

Taiga seeds a set of standards during onboarding, so something sensible is always in place. Two things are worth doing early:

  • Read them, for the same reason as the policies: they are much cheaper to correct before anything is generated against them.
  • Link your design-system repository, if you have one. Agents then build against your real components and tokens rather than a description of them, and the difference in quality between the two is large.

Design system covers both, including deriving standards from a brand guide you already have.

Where to go next

Section titled “Where to go next”