← Back to all sparks
Asana logo

Asana

PMCOLLAB
Velocity6.3

Work management platform for teams

Asana is building the meters and guardrails for its AI Studio credit economy.

ai-studiocredit-governanceenterprise-rbacworkflow-automationcapacity-planningintegrations
Current state
Asana's recent releases cluster around two enterprise concerns: making AI Studio credit consumption legible (department-level allocations, builder-side credit signals, domain limit warnings) and tightening governance through RBAC for view and create permissions. The credit work is monetization plumbing — soft limits and usage estimates that help admins plan spend rather than cap it. Alongside that, the team keeps shipping planning and My Tasks refinements that reduce context-switching.
Where it's heading
The arc points to AI Studio maturing from a feature into a metered platform that enterprises must budget and administer. Each release adds another layer of visibility — by division, by rule, by domain — without yet enforcing hard caps, which suggests Asana is establishing the accounting layer before it monetizes consumption more aggressively. Enterprise governance via RBAC is moving in lockstep, aimed at larger, compliance-sensitive deployments.
Prediction
Expect a true pre-run credit estimate for new rules, which Asana has flagged as on its roadmap, and a likely shift from soft limits toward enforceable budgets once admins trust the accounting.

Recent moves

  1. 11d ago

    ✨ New: AI Studio Department-level Credit Allocations

    Extends AI Studio credit visibility from the builder up to org admins, who can now monitor consumption by division and set soft (non-enforcing) limits. Fits the broader move to make AI Studio's credit economy legible to the people who pay for it, ahead of any hard enforcement.

    View source ↗
  2. 12d ago

    📅 Project dates and milestones: now in your capacity plan, where you need them!

    Pulls project dates and milestones into the capacity-planning view so staffing and delivery timelines sit side by side. Read-only in this first version, it's an incremental step toward connecting Asana's planning surfaces rather than a new capability.

    View source ↗
  3. 19d ago

    Credit awareness for builders: Know when your AI rules will use credits

    Surfaces credit signals where builders create rules — banners flagging AI usage, post-run cost estimates, and warnings at 80% of a domain's limit. Part of the same credit-transparency push, aimed at the rule author rather than the admin.

    View source ↗
  4. 1mo ago

    See your subtasks directly in My Tasks grid✨

    Lets users expand first-level subtasks inline in the My Tasks grid, removing a long-standing context switch. A frequently-requested refinement, scoped narrowly to one nesting level for now.

    View source ↗
  5. 1mo ago

    📣 HubSpot workflows can now do more in Asana with rules and AI Studio

    Deepens the HubSpot integration so Rules and AI Studio can trigger on more CRM objects, map fields with structure, and summarize incoming context. Broadens AI Studio's reach into customer-facing workflows, consistent with positioning it as the automation layer across tools.

    View source ↗
  6. 1mo ago

    🔔 More control over project notifications in Slack

    Replaces all-or-nothing Slack project alerts with per-channel control over which notification types are sent. A direct response to long-running feedback, adding real configurability rather than a new capability.

    View source ↗