Projects

Projects group related tasks, sprints, and members. Every task belongs to exactly one project.

Creating a Project

From the sidebar, click + New Project. A project needs:

Name — shown everywhere in the UI.
Description — optional context; surfaced to Ema and agents.
Visibility — Public (all workspace members) or Private (invite-only).
Cycle — the phase the project is in (see below).

The project slug is auto-generated from the name. URLs look like /{workspace}/{project-slug}/tasks.

Project Cycle

Every project is tagged with a cycle — a lightweight phase marker that helps Ema and teammates understand what stage the work is at:

Cycle	Typical use
Plan	Scoping, kickoff, requirements gathering.
Develop	Active build.
Test	QA, review, acceptance.
Deliver	Shipping, deploy, handover.
Feedback	Post-delivery review and iteration.

You can change the cycle at any time from the project settings.

Views

Each project has three ways to look at its tasks:

Drag-and-drop columns by status. Best for mid-flight work.

📋Kanban

Dense, sortable table. Best for scanning and batch updates.

📜List

Scoped to the active sprint. Shows velocity and scope changes.

🏃Sprint

Private Projects & Access Requests

For private projects, only members and teams explicitly added can see the project. Non-members who hit the project URL see an Access Request screen where they can ask to join. Requests land in the project owner’s inbox with an Approve / Deny button.

Deleting a project is permanent and cascades to all its tasks, comments, and sprint history. Export anything you need first.

Project + Ema

Ema can create, edit, and close projects for you:

“Start a new project called Fitness Tracker with a 2-week sprint.”
“Close the Q1 Marketing project and generate a retrospective.”
“Set the Website Redesign project to the Test cycle.”

See Ema → Overview.