Projects

A project is a logical grouping inside a tenant. Most configuration in SigSentry is project-scoped: log sources, code repos, notification channels, watchdog rules, support desk integrations, API keys, and analyses.

Why projects exist

Most teams manage multiple environments or services that should not share configuration:

• prod and staging have different log sources
• The mobile backend and the web app might point to different repos
• The customer-success project might route notifications to a different Slack channel than engineering

Projects let you keep these isolated without creating multiple tenants.

What's project-scoped vs tenant-scoped

API keys can be tenant-scoped (work across all projects) or project-scoped (only one project) — see Authentication.

The default project

Every new tenant starts with one default project. You can rename it under Project → General. The default project cannot be deleted — this protects against accidentally orphaning the tenant.

Slugs

Each project has a name (display) and a slug (URL- and chat-friendly identifier). Slugs are lowercase letters, numbers, and hyphens. They're scoped to a tenant — prod is unique within your tenant only.

The slug appears in:

• Dashboard URLs: /dashboard/projects/<slug>/...
• Chat command target: /sigsentry analyze ... --project=<slug>
• API requests via the X-Project-Id header (you send the project's ID, not slug, but the slug is the human-readable handle)

Quotas

The number of projects you can have is plan-dependent:

Each project also has its own per-resource quotas (log sources, repos, channels, watchdog rules) — see Plans & quotas.