> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quivly.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects

> Plan and track customer delivery with tasks, milestones, owners, and progress updates.

Use Projects to manage onboarding, implementations, migrations, and success plans alongside your customer records. Each project brings together the work, people, and dates needed to reach an agreed outcome.

Open **Projects** to see work across customers, or open a customer's **Projects** tab to focus on that account.

## Create a project

<Steps>
  <Step title="Choose the customer and name">
    Create a project from the Projects page or a customer's Projects tab. Select the customer and give the project a name that describes the work, such as “Acme onboarding”.
  </Step>

  <Step title="Set up the plan">
    Start from scratch or select a [project template](/product/project-templates). Choose a project owner and set the priority, start date, and target date as needed.

    When using a template, review the copied tasks, assignees, dates, and forms before sharing the project with your customer.
  </Step>

  <Step title="Create and review the project">
    Create the project, then open **Tasks** to organize the work. Customer access is optional; use [Share](/product/customer-portal) when the project is ready for collaboration.
  </Step>
</Steps>

## Organize tasks and milestones

Use **Tasks** for the work someone needs to do and **Milestones** for checkpoints in the plan. Add subtasks within an ordinary task when you need to break the work down further. Subtasks support one level of nesting.

The project **Owner** is responsible for the overall plan. A task's **Assignee** is responsible for that item. Set task priorities, dates, and statuses as the work develops.

Switch between **List** and **Board**, group work by status or milestone, and use **Status**, **Assignee**, and **Milestone** filters to focus the view. Moving a task between status columns updates its status.

<Note>
  Completing a parent task does not complete its open subtasks. Review the confirmation and update the remaining work separately.
</Note>

## Track progress

Project statuses are **Not Started**, **In Progress**, **Completed**, **Cancelled**, **On Hold**, and **Blocked**. Tasks use the same statuses except Blocked.

Progress is calculated from top-level tasks, excluding cancelled tasks. Milestones and subtasks do not add extra weight. A project with no counted tasks shows 0% progress.

Task completion can move a project to Completed. **On Hold**, **Blocked**, and **Cancelled** are manual project states, so keep those up to date when the delivery situation changes.

## Collaborate on the work

Open a task to add comments, upload files, or attach links. Files can be up to **25 MB each**. Comments default to **Internal**; review the **Internal** or **External** label before sharing information with customers.

You can edit or delete your own comments. A file's uploader or a workspace admin can change its visibility or delete it.

Assigning a task to an external contact can grant that person project access and makes the task customer-visible. Use the [Customer Portal guide](/product/customer-portal) to review access and preview what they can see. To make an externally assigned task internal again, remove the external assignee first.

A customer's Done signal records completion on their side. Your team manages the task's internal status separately.

## Post project updates

Open **Updates**, write the latest progress or decisions, and optionally select **On Track**, **At Risk**, or **Off Track**. Posting with a health selection updates the project's health. Check the timeline to confirm the update was saved.

## Save a project view

On the organization-wide Projects page, use search, filters, grouping, sorting, and columns to organize the list. Choose **Save current state as new view**, then select **Private to me** or **Shared with org**.

After changing an existing view, use **Save** to keep the changes or **Reset** to return to its saved configuration. Sharing a view shares that list configuration with teammates; customer portal access is managed separately.

## Build out your project

<CardGroup cols={2}>
  <Card title="Project Templates" icon="copy" href="/product/project-templates">
    Reuse a delivery plan with task owners, relative dates, and forms.
  </Card>

  <Card title="Customer Portal" icon="users" href="/product/customer-portal">
    Invite customers and choose which work they can see.
  </Card>

  <Card title="Task Forms" icon="clipboard-list" href="/product/task-forms">
    Collect information on a task and review customer responses.
  </Card>

  <Card title="Form Templates" icon="file-lines" href="/product/form-templates">
    Save question sets your team can reuse across projects.
  </Card>
</CardGroup>

[Workflows](/product/agents) can also create and update projects, tasks, and milestones through supported steps.

## FAQ

<AccordionGroup>
  <Accordion title="Why can't I find a project or task?">
    Clear the active filters and check the selected view. For customer access, check both the project invitation and the task's visibility in Share.
  </Accordion>

  <Accordion title="What happens when I delete a project or task?">
    Confirm the deletion only when you no longer need the work in the active project. Deleting a project also removes its tasks, milestones, and subtasks from active use; deleting a task removes its subtasks with it.
  </Accordion>

  <Accordion title="The project was created, but customer sharing failed. Should I create it again?">
    Open the existing project and retry the relevant action in Share. Project creation and customer access can have separate outcomes.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.