Integrations and environments
Integrations are where you connect the things outside Taiga that agents need: your source control, your cloud, and the registries your packages come from.
Connections are made once and shared. A cloud account or a registry connected for the organization can be linked to any project, rather than reconnected per project, and it stays manageable after it is created.
Repositories
Section titled “Repositories”A linked repository is the prerequisite for most of what Taiga does.
Detailed planning reads your code before it decides on steps, builds run against a branch of it, maintenance sweeps scan it, and reality documents are derived from it. Without one, a project can produce documents and a backlog but not changes.
Taiga can also provision a repository for you if you are starting from nothing.
Environments
Section titled “Environments”An environment is a place your software runs: development, staging, production, or whatever ladder you use.
They matter more than they first appear, because several surfaces are keyed to them. Deployments are recorded against an environment, monitoring is reported per environment, and a plan made without knowing where the work will run is a plan made against assumptions.
Each environment carries its own configuration for how work reaches it, and can require approval before anything is deployed.
Clouds
Section titled “Clouds”You can connect your own cloud account, or have Taiga provision and manage one.
Bringing your own is the normal enterprise choice: the account stays yours, under your controls, and Taiga is granted access to it. The managed path exists so a project can get to a running environment without waiting on an account-provisioning process, and you can move to your own account later.
Package registries
Section titled “Package registries”If your organization publishes internal packages, connect the registry that serves them.
The clearest case is a design system. When a registry serves it, Taiga installs it like any other dependency, with correct versions and complete type information. When none does, it falls back to cloning the repository and linking from source, which works and makes every build slower.
See design system for what that changes.
Who can do this
Section titled “Who can do this”Managing connections is an administrator capability. Members can see that a repository is connected without being able to change it, which is the right split: the connection is a security boundary, not a project preference.