Skip to main content
Everything under Organisation → Projects is project-scoped. You create a project first; then that project owns environments, ClickHouse Database Configs, connectors (data sources and memory), and signal routing.
Database Config is not a separate top-level product area. It is a resource you create inside a project (same for connectors and bindings).

When to create a project

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.

Create a project

OpenLIT projects list under Organisation
1

Open Organisation

Select Organisation from the sidebar.
2

Review existing projects

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

Create project

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

Select project

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

What a project contains

OpenLIT header with organisation, project, environment, and database selectors

Member access

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.

Environments

How environments partition configs and routing.

Database Config

Add ClickHouse connections on the project.

Connectors

Data-source and memory connectors on the project.

Signal routing

Bind traces, logs, and metrics per environment.