Projects

A project is an umbrella that groups related business records — RFQs, quotes, orders, BOMs, contacts, and products — so you can follow everything that belongs to one customer program, production run, or sourcing effort from a single place. Instead of hunting through six separate lists, you open the project and see all of its linked documents, files, and history together.

Projects are available on the Business plan and up.

What a Project Holds

Field	Description
Code	Auto-generated document number (e.g. PRJ-2026-0001)
Name	Project name (required)
Description	Free-text description (optional)
Status	Active, Completed, or Canceled
Priority	Low, Medium, or High
Manager	A team member assigned as project manager (optional)

Creating a Project

1. Navigate to Projects in the left menu.
2. Start a new project from the list page.
3. Enter a name. Optionally add a description, set the priority (Medium by default), and assign a project manager from your team.
4. Save. The project is created with status Active and receives its code automatically.

Linking Entities

Six entity types can be linked to a project:

• RFQs — see RFQ Management
• Quotes — see Quote Management
• Orders — see Order Management
• BOMs (Business plan and up)
• Contacts — see Contact Management
• Products — see Product Management

There are two ways to create a link:

From the project

1. Open the project detail page and switch to the Entities tab.
2. Open the link entity dialog, search for the record by type, and select it.

From the entity

Each of the six entity types has a project selector on its create and edit pages. Pick the project while creating an RFQ, quote, order, BOM, contact, or product — or change and remove the link later from the same selector.

Linking rules

• An entity can belong to at most one project at a time. If a record is already linked to another project, linking it again is rejected — remove or change the existing link first.
• Links are non-destructive. Unlinking an entity, or even deleting the whole project, never deletes the linked records — they simply lose their project reference.

Tracking a Project

The project detail page has four tabs:

Tab	What you see
Overview	Project info, description, and a summary of linked entities with counts per type
Entities	All linked records grouped by type, with link and unlink actions
Documents	Files attached to the project
Activity	A timeline of every change

The activity timeline records project creation, field updates, status changes, and every entity link and unlink — so you can always reconstruct what happened and when.

Project Status

A project moves between three statuses:

• Active → Completed — the work is done.
• Active → Canceled — the project was abandoned.
• Completed → Active — reopen a finished project.
• Canceled → Active — reactivate a canceled project.

Transitions are validated server-side; the interface only offers the moves that are allowed from the current status.

Finding Projects

The project list offers:

• Status tabs — All, Active, Completed, Canceled
• Search — by project name or code
• Filters — status, priority, and manager
• Sorting — by creation date, name, priority, or status

Typical Workflow

A common pattern for a customer program:

1. Create a project, e.g. "Device X — Pilot Run", and assign a manager.
2. Link the customer contact and the products involved.
3. If you maintain a BOM for the build, link it as well.
4. As you send purchase RFQs to suppliers, set the project in the RFQ's project selector.
5. Incoming quotes and the resulting orders get linked the same way, so the whole RFQ → quote → order chain stays attached to the project.
6. Follow progress from the Overview tab; entity counts show at a glance how many quotes and orders the project has accumulated.
7. When the program ships, mark the project Completed.

Tips

• Use priority and manager filters for a weekly review of what each person is running.
• Treat the Documents tab as the project folder — specifications, drawings, and correspondence live next to the linked records.
• Reopen instead of duplicating — if a completed program comes back, switch it to Active rather than creating a copy and splitting history.