Create a Project

Why projects matter

Projects are one of the main structure layers in Curoxi. Key delivery workflows such as meeting automation, GitHub mapping, release planning, and backlog review all depend on the selected project.

• Projects keep tasks, releases, sprints, and GitHub mappings grouped correctly
• They help delivery work stay separate across customers and workstreams
• They give teams a clearer view of progress and ownership
• They control project-specific task custom fields, releases, sprints, backlog, and attendance

Before you create one

• Select the correct customer workspace first
• Choose a project name that matches the delivery scope
• Make sure the workspace is active before setting up project operations

Best time to create a project

Create the project before you begin delivery setup. That gives you a clean place to attach releases, sprints, GitHub repositories, and AI meeting-note task creation.

• Use separate projects for separate workstreams when the customer has more than one delivery track
• Keep the project name simple and recognizable for both company and customer users
• Remember that customer users now work against the selected project in the top navigation, so clear project names matter

Recommended steps

• Create the project from the customer workspace flow
• Use the project before creating releases, sprints, or GitHub mappings
• Set up task stages and custom fields if the project needs its own workflow or extra task details
• Keep related tasks in the same project so delivery and billing stay easier to review

What outcome it improves

• Cleaner delivery ownership
• Better release planning
• More accurate project-level reporting and automation targeting

Explore Curoxi

Browse the core pages that explain how Curoxi works, how pricing is structured, and how to start a workspace.