Organisation Overview

Organisations in Shield360 are shared workspaces for teams. Inside an organisation, projects own everything you configure for telemetry and memory: environments, Database Configs, connectors, and signal bindings.

Organisation
  └── Project   ← create / select a project first
        └── Environment
              ├── Database Config (ClickHouse app store)
              ├── Connectors (data sources, memory, scanners)
              └── Signal routing (traces / logs / metrics)

Use organisations for membership and workspace boundaries. Use projects when you need separate data boundaries inside the same organisation. Database Config and Connectors are project resources — they appear in the sidebar as documentation topics, but in the product you create them under a project.

What belongs where

Layer	Owns
Organisation	Workspace name, members, invitations; billing/licensing where applicable
Project	Environments, Database Configs, connectors, bindings
Environment	Partition for configs, connectors, and per-signal routing
Database Config	ClickHouse connection on the project (seeded from INIT_DB_*, then managed in UI)
Connector	External backend + credentials + actions on the project

Every organisation has a default project. Existing installations are mapped to a default project and production environment so upgrades keep working.

Common tasks

Projects

Create a project first — Database Configs and connectors live here.

Environments

Partition Database Configs and connectors by environment.

Database Config

Add ClickHouse on a project (seeded from INIT_DB_* then managed in the UI).

Connectors

Data-source, memory, and scanner connectors on a project.

Signal routing

Bind traces, logs, and metrics independently per environment.

Workspace switching

If you belong to multiple organisations, use the organisation selector in the top navigation. Project, environment, database, and connector selectors update based on the selected organisation — the same pattern as the Shield360 dashboard header.