Set up a project

An end-to-end walkthrough — create a project from a template, configure its settings and team, set module access by role, and start working.

A project is the container for one product, line, or variant — its items, its modules, its team, and its compliance posture. This guide stands one up from scratch and gets it ready to work in. For the concepts behind each step, see Creating a project, Project settings, and Module access.

Create the project

Before you start Know what the project represents and whether a template exists for your process.

  1. Choose Create Project from the project selector.
  2. Give it a clear name — typically the product, product line, or variant it covers.
  3. Where one fits, start from a Project Template so it comes preconfigured with item types, workflows, and settings aligned to your process.
  4. Confirm to create it.

Result The project exists and is selectable, carrying whatever defaults the template provided.

Configure its settings

  1. Open the project's settings and complete its details.
  2. Add the team — Add Member for each person who'll work in it.
  3. Confirm the Workflow the project uses, set up its Tags, and set the Compliance Level so the project is measured against the right standard from the start.

Result A project with its team, workflow, tags, and compliance posture defined. See Project settings for the full set of options.

Set module access

Not every project uses every module, and not everyone needs the same access. Access is set per module, by role.

  1. Open the project's module access.
  2. Enable the modules the project actually uses — Requirements, Architecture, Tests, Risks, SBOM, and the rest.
  3. Grant access by role or group with Add Permission, and use Add Override where a specific person or group needs different access from their role's default.

Result The project shows only the modules it uses, and each person sees what their role allows — no more, no less. See Module access.

Start working

  1. Open the first module you'll build in and add a few records (see Working with items).
  2. Start connecting them — link a test to the requirement it verifies — to begin the thread.

Result A live project with real records and the beginnings of a traceable thread, ready for the team to build on. See Your first project for a gentler first pass.

Note When a project reaches end of life, it's retired rather than deleted — its record is preserved for audit. See Archiving.

Where to go next

To control what the project’s activity sends to you and your team, see Manage your notifications.

Was this helpful?