Projects

The Projects admin area is the organization-wide view of your projects — where you create them, organize them, and manage their lifecycle across the whole organization, complementing the in-project settings covered in the Projects section.

The organization-wide project view matters most for the discipline of not deleting things. In a regulated environment a completed project can’t simply be removed — its requirements, signatures, and audit trail are part of a record you may need to produce years later. Archiving is the answer: it retires finished work from daily view while preserving the whole account intact and retrievable. Managing that lifecycle centrally is how a long-lived portfolio stays both navigable for current work and complete for retention obligations, without those two needs fighting each other.

Creating and organizing projects

You create a new project here and organize projects into folders, so a large portfolio stays navigable rather than becoming a flat, unmanageable list. Folders let you group projects the way your organization actually thinks about them — by product line, by team, by program — which matters once you’re running many projects at once.

Project status and archiving

Each project carries a status, and you can see all active projects alongside those that have been archived. Archiving a completed project keeps its full record — its requirements, history, signatures, and audit trail — while removing it from day-to-day views, so finished work is retained for the record without cluttering the workspace. Nothing is deleted; an archived project remains a complete, retrievable account of what was done.

Setting up a project’s governance

Creating a project is the start; what fills it and how it’s governed comes from configuration. Which compliance frameworks apply, which modules are enabled, and who has access are set through the project’s settings and the permission areas — Project permissions and Module access — covered next.