Goal: Understand Vyndra's three-level hierarchy so you can organize work the way real PMOs do.

Who this is for: Anyone setting up Vyndra for more than ~5 projects, or anyone reporting to leadership.

The hierarchy in 30 seconds

Portfolio → Program → Project

• A project is a single piece of work with a beginning and an end. ("Customer Portal Redesign.")
• A program is a group of related projects that share an outcome. ("Customer Experience 2026" — contains the portal redesign, the help center rebuild, and the support-ticket triage tool.)
• A portfolio is a group of programs (and sometimes standalone projects) that share an investment lens. ("Digital Customer Experience" — contains the program above plus the loyalty-app program plus a few standalone projects.)

You don't have to use all three levels. Solo PMs often just use projects. Mid-market teams use projects + programs. Enterprises use the full stack.

When to use what

• Just projects — < 5 active initiatives, single team
• Projects + programs — multiple teams, shared outcomes, need to roll up status
• Full stack — investment-tier reporting, formal portfolio governance, executive dashboards

Steps to set this up

1. Sidebar → Portfolios → + New Portfolio if you need one.
2. Inside that portfolio, + New Program to create a program.
3. Inside the program, click Add Project and pick from existing or create a new one.

You can also leave projects standalone (not in a program) and attach them directly to a portfolio. Vyndra handles both.

What's next

→ Read Submit and triage a demand to learn how new project ideas enter the system in the first place.