LoginSign Up
← Back to all sparks
Asana logo

Asana

PMCOLLAB
Velocity6.3

Work management platform for teams

asana.com ↗

Asana lets Division admins run their own custom roles, on top Enterprise plans only.

work-managementgovernancepermissionsai-studioenterprisestructured-data
◆Current state
Asana's fall releases split between new structure and tighter control. Tables arrived on October 29 as a new object type; since then it has added a Client portal tab in Inbox, collapsible headings in Pages and hourly credit limits for AI Studio automations. The November 12 release lets Division Admins assign roles and build custom roles from Member or Guest, with one role per person across all Divisions.
◆Where it's heading
The governance thread is getting more granular: rules that run with their owner's current permissions, credit caps per automation, and now role control pushed down to Division level. Asana is building the admin layer large companies need before they let AI Studio and new objects like Tables spread across departments.
◆Prediction
Expect further admin and permission controls for Tables and AI Studio, likely gated to Enterprise tiers as this one is.

◆Recent moves

  1. 1d ago

    Role-based access control now available for Divisions

    Division Admins can now manage roles and create custom roles from the Member or Guest base, with one role per person across Divisions. It continues Asana's push of permission control down to sub-org level, gated to Enterprise with the Permissions add-on and Enterprise+.

    View source ↗
  2. 3d ago

    🚦 Keep AI Studio credit use in check with rate limiting

    Every AI Studio automation now has a credit limit for a rolling hour, with extra runs queued for the owner to resume or cancel within 24 hours. It is a billing guardrail rather than a new capability, and Asana says plainly it is not a spending cap.

    View source ↗
  3. 8d ago

    📥 Client portal activity now has its own spot in Inbox

    A dedicated Inbox tab collects comments, uploads and task updates from client portals, so client activity no longer sinks under internal notifications. It is the first visible follow-up for Client Management customers in this run, and it is gated to that license.

    View source ↗
  4. 9d ago

    🗂️ Collapsible headings are now live in Pages

    Pages can now fold sections under Heading 1 to 3, per viewer and without changing what others see. It is a community-requested reading aid that treats Pages as long-form docs, a small step next to the Tables launch.

    View source ↗
  5. 15d ago

    Introducing: Tables

    ⚡ SPARK

    Tables is the first new object type in this run of releases, after a fall spent on subtask structure and permissions. It extends Asana from tasks and projects to the reference records behind them, and hands that data to the AI Teammates launched in the summer.

    View source ↗
  6. 29d ago

    :puzzle_piece: Subtask types now follow their parent, across projects

    A second subtask fix in a week: the parent task now decides a subtask's type, so the same parent behaves the same in every project it lives in. Custom task types get an inherit-or-basic toggle, which keeps request-style workflows (a Laptop Request with plain fulfillment tasks) clean. It continues the fall pattern of tightening the structure that automations and AI Teammates depend on.

    View source ↗