[Change] Teamless Projects

English Forum Developers & API Changelog
18

Hi @Phil_Seeman ,

We’ve heard your feedback about the importance of team-project associations in existing integrations, and we’ve revised our plan accordingly. Here’s a summary of what changed

What’s staying the same:

  • Newly created projects will no longer require a team. The project.team field will be null by default on new projects.

  • All API clients should be prepared to handle a null value for project.team.

What changed from the original plan:

  • Team associations are still supported. You can still set project.team on both create and update. We are not deprecating the ability to associate a team with a project.

  • No endpoint deprecations. We are no longer planning to deprecate GET /teams/{team_gid}/projects, and the project creation and update endpoints will continue to support the team field as before.

  • No breaking changes to write operations. Setting a team on project creation will continue to work as it does today — the team will be set as the project’s team, not converted to a membership.

The key change for API clients: If you read project.team, your code must now handle a null value, since newly created projects won’t have a team by default. Projects created before the rollout will retain their existing team association.

We’ve updated the original post above to reflect this revised plan. The core timeline remains the same: gradual rollout beginning February 2026, completing by April 2026.

The original post has been updated to reflect these changes.

Thank you for your feedback. We’re committed to evolving the Asana while minimizing disruption to existing integrations.

4 Likes