Bring Private Projects Back to Teams

Before the Teamless Projects change and the new navigation, a private project created within a team appeared under that team in my own sidebar, visible only to me. That was the whole point: I could keep a project private AND keep it organized where it belongs.

Now, because team navigation only shows projects the team itself has access to, private projects don’t appear under their team at all. By definition, a private project doesn’t grant the team access, so there is no longer any way to keep a project both private and organized under its team in navigation.

This isn’t a layout preference. It’s a functional regression. The old model separated two different things: who can see a project (access) and where it lives (organization). The new model conflates them, and private projects fall through the gap. People create private projects and then can’t find them without knowing the name or going through a multi-click process.

The suggested workarounds don’t solve it:

  • Starring: doesn’t scale, and a flat starred list loses the team context that made navigation work in the first place.
  • Project Browser: finding your own project shouldn’t require leaving your workflow to search a separate browser.
  • Portfolios: this one keeps getting offered in other threads, and it’s not an answer. Portfolios require Advanced or above. Anyone on Starter has no access to portfolios at all, so for a large portion of your customer base this “solution” doesn’t exist.

The ask: restore the ability for a private project to appear under its team in the owner’s own navigation, visible only to people with access. Privacy should control who sees a project, not whether its owner can find it.

5 Likes

Thanks, @Christine_Bolton, I voted.

@Forum-team, Did something change with how projects appear in Team pages? There was a new topic added today and I think one or two other posts recently around this.

Thanks,

Larry

1 Like

Yes, I too have noticed this. And run into many issues with it. I have no work around. Like you said the work arounds you mentioned it, not resolve this. As Asana continues to push the use of Portfolio, that requires an upgrade, more and more is breaking with the Teams model many of us rely on.

1 Like

Since the recent Asana update, many of my private projects no longer appear under their associated teams, even though they are correctly assigned.

I manage an architecture firm with numerous projects organized by team. This change has made our daily workflow significantly more complicated.

Please restore the ability to display all projects under their associated teams, including private projects, without changing their access permissions.

This is essential to our workflow.

1 Like

Hi everyone,

There have been several changes since the introduction of the teamless projects, and we love hearing your feedback!

Because of this, team pages only show projects based on two signals:

  • The project is shared with the team
  • The project is associated with the team (for context)

So a project may not appear on a team page even if you have access to it. You can still find all projects you can access in the Project Browser.

Keep voting to have your voices heard! :heart:

To learn more about Teamless Projects click here.

Best,
Ren

1 Like

Thank you for your detailed explanation.

Regarding " Project Browser" one thing that caught my attention was this description:

shows all projects you have access

I tried it, but it seems that I can’t find projects within the organization that I’m not involved in. It’s a slightly puzzling phenomenon.