Create & organize projects
Create projects from the organization-wide view, keep a large portfolio navigable with folders, archive completed work without losing its record, and govern each project from the start.
The Projects admin area is the organization-wide view of your projects — where you create them, organize them, and manage their lifecycle, complementing the in-project settings in the Projects section. This guide covers standing a project up, keeping a growing portfolio manageable, and retiring finished work the right way. For the reference, see Projects.
Create and organize projects
As the number of projects grows, how they’re organized is what keeps the portfolio usable.
Before you start Open Administration and go to Projects. You'll need administrator access.
- Create a new project.
- Organize projects into folders — by product line, team, or program — so a large portfolio stays navigable rather than a flat, unmanageable list.
Result A portfolio grouped the way your organization actually thinks about its work. See Projects.
Manage status and archiving
Finished work shouldn’t clutter the workspace, but in a regulated system it can’t simply disappear either.
- Track each project's status, and view active projects alongside those that have been archived.
- Archive a completed project to keep its full record — requirements, history, signatures, and audit trail — while removing it from day-to-day views.
- Retire projects by archiving rather than deleting: nothing is removed, and an archived project stays a complete, retrievable account of what was done.
Result Completed work is retained for the record without cluttering the workspace.
Govern the project from the start
Creating a project is the beginning; what governs it is set right after.
- Decide which compliance frameworks apply to the project — see Compliance frameworks.
- Set which modules the project uses and the access to each, through Module access.
- Set who can do what in the project through Project permissions, on top of each person's role.
Result A project that's governed from the moment it exists, not configured as an afterthought.
Note Archiving over deleting is the regulated default, not a preference. A completed project's record — its signatures and audit trail included — has to remain retrievable, so a project is retired by archiving it, never by trying to remove it.
Where to go next
How access resolves across role, project, and module is laid out in Access rules. To set up what fills a project — its structure and content — from the in-project side, see Set up a project in the Projects section.