Portfolios: planning for multiple teams

A portfolio is a slice of your workspace — a chosen set of projects, the people who work on them, and the planners who can see them. Portfolios let a larger organisation run several teams, departments, or clients side by side in one Mermix workspace, without everyone tripping over each other's plans.

If you're a single team, you may never need more than the one portfolio you start with. If you run several, this is how you keep them tidy.

What a portfolio contains

Each portfolio groups four things:

• Projects — which Jira projects (and issue types) belong to this team.
• Resources — the people who appear on this portfolio's calendar.
• Planners — who's allowed to open and edit this portfolio.
• Budgets (optional) — a budgeted cost and sold value per project, which powers the profitability report.

A person or a project can belong to more than one portfolio. That's deliberate — it supports functional teams (the same project split into Frontend, Backend, and QA portfolios by issue type) as well as simple per-team or per-client splits.

Switching between portfolios

When you have more than one portfolio, a selector appears at the top of the calendar. Choose a portfolio to see just its people and work; choose All portfolios (Admins) to see everything at once. Reports, the backlog, and the Copilot all follow the portfolio you're viewing, so the numbers always match what's on screen.

Log in with two or more portfolios and you'll first land on a portfolio overview — a health card per portfolio showing its status at a glance. Click one to dive in, or open the combined view.

Capacity across portfolios

Because someone can work across portfolios, Mermix keeps their capacity honest. If a person is booked in another portfolio, that time still counts against them here — shown as a subtle marker on their row — so you won't accidentally double-book them. The Copilot and the overallocation indicators account for this automatically.

Setting up portfolios

Admins manage portfolios in Settings → Portfolios:

1. Create a portfolio and give it a name.
2. Assign its projects and issue types, its resources, and the planners who can access it.
3. Optionally add per-project budgets for profitability reporting.

The first portfolio (your workspace's default home) already exists from onboarding, so new projects have somewhere to live from day one.

How many portfolios you get

As many as you need — portfolios are unlimited on every plan, including the trial.

Organise your workspace the way your teams actually work, not the way a plan limit makes you. If that means one portfolio, fine; if it means fifteen — one per department, per client, or per functional team — that's fine too, on any plan.

The only thing plans differ on is the number of resources you schedule. See the trial guide for the current plans.

When you don't need them

Portfolios are optional. A single team can run happily on the one default portfolio and never touch the selector. Reach for portfolios when different groups of people need to plan different projects without seeing each other's noise.