Employee project portfolio

The project portfolio is the company-wide record of what your teams are changing. Employees read it on the company home under People → Projects; a portal manager curates it in Settings → Projects.

It is published knowledge, not a work tracker. A project carries an outcome, an accountable owner, contributors, milestones and a reported health — there are no tasks, assignments, schedules, or costs.

Turn it on

The portfolio is off until an administrator enables the portal_projects feature. While it is off, neither the employee destination nor the manager surface is reachable, and nothing is stored.

Create and publish a project

Open Settings → Projects and choose Add project. A project needs a title and an accountable owner; outcome, summary, business area, audience and health are optional. The owner must be an active member of your organization.

A new project starts as a draft and no employee can see it. Choose Publish when it is ready — this is a separate permission from editing, so an editor can prepare a project that only a publisher may release.

Afterwards you can mark a project completed (it stays visible — finished work is worth publishing) or archive it (employees no longer see it). Archiving is final: to bring something back, publish a new project.

Decide who sees a project

Leave the audience empty and every employee sees the project. Choose a group to narrow it to that group's members. Audience is applied when the portfolio is read, so a project outside someone's audience never reaches their browser — not even its title or its existence in the summary counts.

Contributors and milestones

Contributors record who is working on a project and in what capacity (lead, contributor, or sponsor). Being listed grants no permissions.

Milestones carry the progress. Each has a title, an optional due date and a progress percentage, and can be marked done. The percentage shown on a project card is calculated from its milestones — a project with no milestones shows no progress bar rather than a misleading 0 %. The next milestone on a card is the earliest-dated one that is not yet done.

What employees see

Employees get a read-only view: four summary tiles (active projects, on track, needs attention, and how many people are contributing), filter chips for all projects, their own projects, projects needing attention, and completed work, then a card per project. Opening a card shows the outcome in full, the milestone list, and the people on the project.

Every project has a stable address of the form /portal/projects/PRJ-0007, so a link can be shared. What a colleague sees when they open it still depends on their own access: a project outside their audience shows as not found.

Who can do what

Every change is recorded in the audit log.