LoginSign Up
← Back to all sparks
Asana logo

Asana

PMCOLLAB
Velocity6.3

Work management platform for teams

asana.com ↗

Asana doubles down on rules-driven automation while loosening the old project-team coupling.

workflow-automationrules-engineenterprise-rbacorganizational-structurepsasubtasks
◆Current state
Asana is shipping at a high cadence on two parallel tracks. The first is deepening its automation engine — pausable rules, rule duplication across projects, scheduled triggers that now act on tasks already in a project, and rule actions that bind to project-template roles. The second is reshaping enterprise governance and data model, with RBAC view permissions in Release Preview and Teamless Projects loosening a long-standing structural constraint.
◆Where it's heading
Rules are being built into the automation backbone of the product — closer to a no-code workflow runtime than a notification system. Teamless Projects removes a constraint that made enterprise rollouts awkward, and the Timesheets and Budgets add-on going GA pulls Asana into PSA-adjacent territory. The pattern is consistent: move from a flat, team-scoped task tracker toward a configurable platform that can be sold up-market.
◆Prediction
Expect future rule actions to look more agentic — AI-driven branching, conditional approvals — and an RBAC-aware automation surface so admins can govern who can trigger what across the workspace.

◆Recent moves

  1. 3d ago

    ⏰ Scheduled Triggers V2: Now run scheduled rules on the tasks already in your project

    Scheduled Triggers V2 closes the most-requested gap from V1 — rules can now act on tasks that already exist in a project, not just newly arriving ones. It is a meaningful step in turning Rules into a general-purpose scheduling layer rather than only a reactive one.

    View source ↗
  2. 5d ago

    📣 RBAC View Permissions for Enterprise+ is now in Release Preview!

    RBAC view permissions hit Release Preview for Enterprise+ ahead of a June 2 general rollout, replacing manual workarounds that large customers have long used to model contractor and student access. It is a continuation of Asana's enterprise hardening rather than a directional change.

    View source ↗
  3. 12d ago

    Subtasks now show parent project and fields in the task pane ✨

    Subtasks now inherit and surface parent project and custom field context up to five levels deep, removing a friction point that nearly every active Asana customer hits at scale. A clear quality-of-life win that does not change the trajectory.

    View source ↗
  4. 15d ago

    Introducing Teamless Projects

    ⚡ SPARK

    Teamless Projects breaks the long-standing rule that every project must live inside exactly one team — projects can now exist independently and be shared with one or more teams or individuals. Structurally, this is the most significant change to the Asana data model in years and unblocks cleaner cross-functional and external-collaborator workflows.

    View source ↗
  5. 1mo ago

    Rule actions can now target Project Template Roles

    Rules can now reference roles defined on project templates instead of hard-wired users, so an action that assigns the 'Reviewer' role resolves correctly when a template is instantiated. A small but compounding extension of the rules engine's expressiveness.

    View source ↗
  6. 1mo ago

    Timesheets and Budgets add-on opens to all customers with a free trial

    The Timesheets and Budgets add-on moves from gated availability to a free trial open to every customer, pulling Asana further into professional-services-automation territory. It pairs with the broader move up-market that the RBAC and Teamless Projects work is also serving.

    View source ↗