Projects

A project is the narrowest container where intelligence tools execute. It belongs to exactly one organization, inherits that org’s credits, and keeps runs, exports, and collaboration scoped to a brand, initiative, or client engagement.

Why projects exist

Spreadsheets and chat threads lose context fast. Projects bundle inputs (briefs, URLs, competitive notes) with outputs (research packs, hooks, scripts) so strategists can reopen the same workspace next quarter without rebuilding history.

Creating a project

Navigate to All projects (/org/your-organization-slug/projects) and choose New project when quotas allow. Direct links such as /org/your-slug/projects/new skip one hop but enforce the same limits.

Role required: Project creation requires a role with org content edit permission and sufficient plan quota.

If creation is disabled, the banner typically cites plan caps—resolve via Credits & billing or archive unused initiatives.

Working inside a project

Once inside, you will see grouped routes—Research, Creative, Quality, Delivery—mirroring how Tools overview documents layers. Pick a tool, supply structured inputs, then monitor Runs & status for completion.

Outputs remain attached to the project so teammates can audit what shipped and rerun with modified assumptions.

Practical habits

• Name projects after client + initiative + quarter so reporting stays searchable.
• Duplicate successful projects when you recycle frameworks—faster than cloning scattered docs.
• Cross-link stakeholders to this Help article when they ask why multiple projects belong to one org.

Related reading

• Tools overview — capabilities and credit estimates
• Organizations — ownership and URLs
• Project access requests — when members cannot access needed projects