Projects
The private container for every launch workflow.
What it does
Stores project basics, status, profile completeness, linked module data, and owner/workspace access.
When to use it
Create one project per launch, update, website, product, game, or client release.
Steps
- Add name, type, tagline, description, audience, and optional URL.
- Open the project overview.
- Move through module cards as your launch matures.
Common mistakes
- Using one project for unrelated launches.
- Leaving the website URL blank before running Auto Audit.
Beta limitations
- Archived projects are soft-archived; they are not hard-deleted by default.