Skip to content

Projects

Everything under Organisation → Projects is project-scoped. You create a project first; then that project owns environments, ClickHouse Database Configs, connectors (data sources, memory, and scanners), and signal routing.

Organisation
└── Project ← create this first
├── Environments
├── Database Configs (ClickHouse)
├── Connectors (data sources, memory, scanners)
└── Signal routing

Create a project for:

  • Separate teams that share the same organisation
  • Customer-specific deployments
  • Workloads that should use different ClickHouse Database Configs

Use environments (production, staging, …) inside a project when you need multiple backend targets without splitting projects. See Environments.

Shield360 projects list under Organisation
Open Organisation

Select Organisation from the sidebar.

Review existing projects

Use the projects list to see projects already available in the organisation.

Create project

Click Create project, enter a project name, and submit.

Select project

Use the project selector in the top navigation to make the project active. Then pick an environment.

ResourceDescription
EnvironmentsNamed partitions (production, staging, …)
Database ConfigsClickHouse app-store connections per environment
ConnectorsData-source (Tempo, Loki, Prometheus, Jaeger, ClickHouse), memory (Claude, Mem0, Zep), and scanner (Trustabl)
Signal bindingsWhich connector serves traces / logs / metrics per environment
Shield360 header with organisation, project, environment, and database selectors

Project access controls which organisation members can use a project. Existing organisation members are assigned to existing projects during migration so current installations continue to work. New members can be invited to the organisation first and then granted access to specific projects as needed.