Creating a project

A project is the container for a body of work — a product, a product line, or a variant. Creating one sets up its identity and the defaults everything inside it will inherit.

Starting a new project

Create a new project from the project administration area. You’ll be asked for a few essentials:

• Project Name — the human-readable name, usually the product or program
• Project Code — a short identifier (for example, ALPHA) used as a prefix and shorthand for the project
• Description — a brief summary of what the project covers
• Visibility — who the project is visible to within the organization
• Parent Folder — where the project sits in the project tree (see The project tree)

Setting the defaults

The same step establishes how the project behaves:

• Enable versioning for items — turns on item version history for the project, which is standard for controlled work
• Default Role for New Members — the role newly added members receive unless set otherwise
• Initial Team Members — people to add to the project right away, with the option to auto-add organization administrators

These are starting points, not permanent choices — each can be revisited in Project settings once the project exists.

Working to your standards from the start

Where your organization has defined compliance profiles and templates, a new project can inherit them — item types, workflows, and controls aligned to your process — so the first record you create is already governed correctly. How those profiles are defined is covered in the Administration and Compliance sections.