Danger Zone
Project metadata editing, bulk-purge of components, and project deletion — all the destructive operations grouped in one place
The Danger Zone page concentrates destructive operations: editing project metadata, purging all data of one component type, or deleting the whole project.
Operations on this page are permanent. Most require typing confirm
into a confirmation field before they fire.
Project Details
Editable fields for the project itself:
| Field | Notes |
|---|---|
| Name | Display name |
| Slug | URL identifier; must be lowercase, alphanumeric + hyphens |
| Description | Optional |
Click Save Changes to update. If the project is the default project, the slug field is locked — you can't change it.
Purge Component Data
A grid of six cards, each representing one type of project data (Analyses, Log Sources, Repos, Channels, Watchdog, API Keys). Each has a Delete All button.
Clicking a Delete All button reveals an inline confirmation:
- Type
confirmin the input - Click Confirm purge
- All data of that type is deleted for this project — irreversibly
This is useful when migrating projects, decommissioning a service, or starting fresh after a bad configuration.
Delete Project
A full-width card at the bottom of the page. Click Delete Project
to start the deletion flow. As with purges, you have to type
confirm to fire it. After confirmation:
- All project resources (analyses, log sources, repos, channels, watchdog rules, API keys) are deleted
- The project record itself is removed
- You're redirected to
/dashboard/projects
The default project cannot be deleted — its delete button shows "Cannot delete the default project" instead.
Required role
| Action | Required permission |
|---|---|
| Edit project details | config:write (admin, member, owner) |
| Purge component data | config:write |
| Delete project | project:delete (owner only) |
If you're not the owner, the Delete Project button is hidden entirely.
What happens to billing on deletion
Project deletion doesn't change your billing — your tenant's plan and analysis quota are unaffected. The deleted project's analyses still count against historical usage; only future activity stops.