Projects

A project is the container for a product, a product line, or a variant — whatever matches your process. Everything you author lives inside a project, and projects are organized in a hierarchical tree of folders so a large portfolio stays navigable.

This section covers the full lifecycle of a project, from creation through configuration to archiving.

The project as the unit of governance

Everything you author in TraceUnified lives inside a project, and that boundary is what makes access, workflow, and compliance manageable at scale. A project maps to whatever unit matches your process — a product, a product line, or a variant — and it carries its own team, its own configured workflow, and its own compliance settings. Because the project is the container, permissions and governance are applied where they make sense rather than one blanket policy for the whole organization.

Organized in a navigable tree

A large portfolio becomes unmanageable as a flat list. Projects live in a hierarchical tree of folders, so a program with dozens of products and variants stays navigable, and structure can mirror how your organization actually thinks about its portfolio. Moving through the tree is how you switch context between the products you work on without losing your place in each.

Configuration and the full lifecycle

A project isn’t static. Its settings govern details, team membership, the workflow records follow, tagging, and compliance alignment — and module access controls which capabilities the project uses and who can reach them, by role. At the end of its life a project is archived rather than deleted, which retires it from active work while preserving its complete record for retention and inspection. That full arc — create, configure, control access, archive — is what keeps a long-lived regulated portfolio both organized and auditable.

What’s in this section

• Creating a project — starting a new project and its defaults
• The project tree — organizing and navigating projects in folders
• Project settings — details, team, workflow, tags, and compliance
• Module access — choosing which modules a project uses, by role
• Archiving — retiring a project while preserving its record
• Set up a project — a step-by-step walkthrough from creation to a working, access-controlled project