Project metadata
Name, slug, and description — the fields that identify a project across the dashboard, API, chat, and webhooks
Three fields identify a project. They're set at creation and editable later from Project → Settings → General.
Fields
| Field | Limit | Notes |
|---|---|---|
| Name | 255 chars | Display name shown in the dashboard, chat, and notifications. "Checkout API", "Marketing Site", "Internal Admin Tools" |
| Slug | 100 chars, lowercase + hyphens | Stable identifier used in URLs, chat commands (--project=<slug>), and X-Project-Id API header references. Auto-generated from name on creation; editable later |
| Description | Free-form text | Optional. Helps team members understand the project's purpose. Not sent to the AI |
Choosing a slug
Slugs need to be unique within your organization. They appear in:
- Dashboard URLs:
/dashboard/projects/<slug>/... - Chat commands:
@SigSentry analyze "checkout errors" --project=<slug> - Watchdog rule references in webhooks
Pick something short and memorable. "checkout" beats "checkout-api-prod-us-east".
Renaming a project
Editing the name is safe — display only, no impact on integrations.
Editing the slug rewrites all URLs and breaks any saved chat commands or scripts that referenced the old slug. The dashboard issues a warning before you save. We recommend doing slug renames during low-activity windows.
Default project
Every organization gets a default project at signup, named after your company. You can rename it, edit its slug, or delete it once you've created another project — the default flag transfers automatically to the next project.