---
title: "Projects and workstreams"
description: "How projects and workstreams organize the work of standing up new services in Vigilis, and how templates, duplication, and archiving fit together."
---

> Documentation Index
> Fetch the complete documentation index at: https://support.vigilis.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects and workstreams

Projects live at `/projects`, under Operations in the sidebar. Projects is part of the Projects add-on and is intended for organization admins, so depending on your plan and role you may not see it. If you expect it and it is missing, see [Roles and permissions](/navigation/roles-and-permissions/), ask an organization admin at your company, or ask your provider about the Projects add-on.

## What a project is

A **project** is a top-level engagement, for example standing up service at a new site.

Each project breaks down into **workstreams**, which is where the actual task work lives. The usual pattern is one workstream per service, plus any standalone workstreams the engagement needs.

## Templates, duplication, and archiving

- **Templates.** A template is a reusable checklist of task steps you apply to a workstream, so you are not rebuilding the same sequence of steps for every project.
- **Duplication.** Projects can be duplicated when a new engagement closely matches one you have already run.
- **Archiving.** Projects can be archived without losing their history.

## How projects relate to tasks and comments

The individual action items inside a workstream are tasks, which everyone at your organization can see on `/tasks`. See [Tasks and tickets](/operations/tasks-and-tickets/).

When a service belongs to a project workstream, the service and the workstream share a single combined comment feed, so the full conversation appears on both pages. See [Comments and notifications](/operations/comments-and-notifications/).

## Common questions

**What is the difference between a project and a workstream?**

A project is the top-level engagement, for example standing up service at a new site. Workstreams sit inside a project and are where the actual task work lives, typically one workstream per service plus any standalone workstreams.

**Can I reuse the same set of steps on every project?**

Yes. A template is a reusable checklist of task steps you apply to a workstream, so a project can be built from a template rather than assembled by hand each time.

**What happens to a project's history when I archive it?**

Projects can be archived without losing their history, so an archived project keeps its record of what was done.

Source: https://support.vigilis.io/operations/projects-and-workstreams/index.mdx