Loading
PLATFORM
CAPABILITIES
ASANA AI
PLANS
Company Type
Teams
Industries
Use Cases
LEARN
SUPPORT
SERVICES
Help Center
search-icon

Topics

Teamless projects

In This Article

Asana has updated how projects work with teams. Projects no longer need to live inside a team, giving you more flexibility and helping keep team pages focused on relevant, shared work.

This guide explains what’s changing, how to work with teamless projects, and how we preserve important project–team context.

What are teamless projects?

Previously, every project in Asana belonged to a single team. With the teamless experience, projects can exist independently and be shared intentionally.

A project can now:

  • Exist without being housed in a team
  • Be shared with one or more teams
  • Be shared directly with individual people

This separates where a project lives from who has access to it.

Create a project without a team

When creating a new project, adding a team is optional.

To create a teamless project:

  1. Click + Create → Project
  2. Choose a template or start from scratch
  3. Optionally:
    1.  Add individuals and/or teams as project members during creation
    2. Or, skip selecting a team and just go straight to a project

Find your projects

Project Browser

The Project Browser shows all projects you have access to—whether or not they’re shared with a team.

If a project isn’t on a team page, you’ll still find it here.

Team pages

Team pages display projects that are relevant to the team, including projects shared with the team as well as other important work associated with it.

Preserving project–team context with Associated team

We know many projects were historically tied to a specific team, and that context is still valuable for filtering, reporting, and understanding where a project came from.

To make sure no project–team context is lost, Asana continues to show this information using the Associated team field.

What this means

  • If a project previously lived in a team, that team will appear as its Associated team

  • This preserves the historical connection between a project and its former container team

  • You can continue to:

    • Filter projects by team

    • Group projects in views and reports

    • Maintain continuity for existing workflows and reporting

Important to know

The Associated team field:

  • Reflects organizational context only

  • Does not control permissions or access

  • Does not determine where a project lives

  • Does not automatically share the project with that team

Access is still managed explicitly by sharing the project with people or teams.

Updating the Associated team

You can update the Associated team at any time from the project details as a project’s primary context evolves—without affecting visibility or access.

Frequently asked questions

Why don’t I see a project on my team page anymore?

Team pages may not show every project you have access to. If you don’t see a project where you expect it, check the Project Browser to find all projects available to you.

Does this change who can access my projects?

No. Access only changes if you explicitly share or unshare a project with people or teams.

Can a project be associated with a team but not shared with it?

Yes. The Associated team preserves context but does not grant access.

Can a project be shared with multiple teams?

Yes. When shared with multiple teams, it will appear on each team’s page.

Related articles

Loading
Teamless Projects in Asana: Create & Share Projects Without Teams