Asana AI Teammates

Asana’s AI Teammate works like a coworker, with its own login and permissions.

Asana assigns its AI Teammates tasks like people, gives them a new hire’s permissions, and bills each finished job as a request. Here is how that one choice shapes access, approvals, coaching and price, and where it leaks.

Image: Asana · AI Teammates product page

At a glance#

What it does: Takes a task assigned to it in Asana and reads the tasks and projects it has been invited to. It drafts documents and plans, posts progress in the task’s comments, and can act in Google Drive, Gmail, Slack, HubSpot and other connected apps.
Who it’s for: Teams on any paid Asana plan. Asana ships 30+ prebuilt Teammates for marketing, operations, IT and specific industries, with 160+ skills in its library, and teams can build their own.
Price: Included in every paid plan since mid-September 2026: 5 AI requests per user per month, pooled and capped at 50 per organization on Starter and Advanced, 250 on Enterprise. Extra requests cost $0.50 prepaid or $0.60 pay as you go. A request is one finished unit of work.
Model: Claude Opus 4.6 in a multi-agent setup on Claude Managed Agents, per Anthropic’s customer page. Asana picks the model. Its FAQ lists OpenAI, Anthropic, AWS Bedrock, Google Gemini and open-weight models served by Fireworks.ai as partners.
Takes actions?: Yes. In Asana it edits tasks and posts comments at the access level it was given. In connected apps it acts as the person who asked, through that person’s own account; reads run freely and writes ask for approval by default.
Claimed results: Asana says early users finished tasks twice as fast. AI Studio and AI Teammates drove about 25% of Asana’s net new ARR in its fiscal second quarter of 2027, reported in September 2026. More than 25% of its $100,000-plus customers have bought one of them.
Launched: Announced September 25, 2025 as a beta for AI Studio Pro customers. Live for everyone on March 17, 2026 as a sales-quoted add-on with 21 prebuilt Teammates. Folded into every paid plan in mid-September 2026.

Why it matters#

Most products put the agent in a chat box beside the work. Asana put it inside the work. An AI Teammate has a profile and a seat in the project. You assign it a task the way you would assign a colleague. It reads what it has been invited to read, posts in the task’s comments, and gets better when you tell it what you liked.

Asana built the agent as a coworker with a login. It reads what it has been invited to read, writes in task comments, asks before some actions, learns from feedback, and bills per finished request. Its main leak comes with the comment box: a reply is visible to everyone on the task.

How it works#

What happens when a request reaches Asana AI Teammates.

Assign the task
A marketer assigns “Draft 2026 Summer Campaign Brief” to the Campaign Brief Writer, a prebuilt Teammate, with the sources listed in the description. Rules, forms and recurring tasks can assign work the same way.
Read within its access
The Teammate answers only from what both it and the requester may see. It was added to the private marketing team and given Viewer access to the private launch calendar, the way a new hire would be.
Load a skill and draft
A Skill is a self-contained module of guidance and tooling the Teammate loads when the task needs it. With its behavior guidance (flag gaps, follow the template) it drafts the brief as a Google Doc through the requester’s own Google connection.
Ask before writing to an app
Creating that doc is a write action, and writes in connected apps pause for the requester’s approval by default, with the proposed action shown in the task. A declined action is skipped.
Report in the comments
The Teammate proposes three reviewers, links the deliverable and assigns an approval task, all as comments that everyone with access to the task can read.
Get coached, then get billed
A reviewer writes “Incorporate the feedback we left,” and the revision counts as one AI request, while “remember this format next time” is filtered out and costs nothing. Only admins and editors can commit feedback to the Teammate’s permanent memory.

The decisions worth studying#

What they chose, why, and what it costs.

1It gave the agent a new hire’s permissions, and the same comment box

A new AI Teammate sees public tasks and projects. For private work it must be invited as a member or collaborator. It works at the Editor, Commenter or Viewer level it was given, and Asana says it cannot raise its own permissions. When you assign it a task, it answers only from objects both you and it can access, so nobody can use it to look up something they could not open themselves.

In other apps the same rule holds. Every integration acts as the person who triggered it, through that person’s own connected account, so two people can get different results from one Teammate.

The cost is the reply. Asana’s guide warns that a Teammate’s comments are visible to everyone with access to the task, and asks you to consider the audience before you ask. Those people can include someone who cannot open the sources. Asana checks who may read the inputs and leaves who reads the output to you.

An Asana task where the Campaign Brief Writer AI Teammate posts comments, a linked Google document and an approval task, next to private team and project access. — The draft, the reviewer proposal and the approval task all land in the task’s comments, where every collaborator can read them. The Teammate’s access to a private team and private project sits in the panel below. Asana recording · 2:35

2Approval is tied to who gains access, and it belongs to each person

Inside Asana, approval keys on visibility. Removing a collaborator or project member always asks first. Assigning a task or adding a collaborator asks only when someone would gain access they did not have. Deleting a task asks unless the Teammate created it. My read: in a work tool the risky move is changing who can see what, so Asana gates that and lets ordinary edits through.

In connected apps, approval is a per-person setting. Reads are always allowed. Writes and deletes ask by default, and a newly added write action arrives set to ask. Each person sets these for their own connection. Asana notes many people give Dash, their private assistant, more room than Teammates working in shared projects.

Two gaps. Adding a task to another project skips approval under a flag the docs label temporary. And authorizing an app for one Teammate authorizes it for all of your Teammates, so a Gmail connection made for one job is available to every Teammate you work with.

Asana · Teammate profileProduct screenshot

The Teammate’s written rules, its access list (Member of a private team, Viewer on a private project, Editor on a public one) and its memories, each citing the tasks it learned from. Asana recording · 3:24

3It sells finished work, and gives the first taste away

Asana bills by the AI request, defined as a single, successful unit of work. A finished task, a follow-up question and a revision each count. A failed or cancelled run does not, and neither does a coaching note like “remember this format next time.” Since mid-September 2026 every paid plan includes 5 requests per user per month, capped at 50 per organization on Starter and Advanced and 250 on Enterprise. Beyond that, requests cost $0.50 prepaid or $0.60 on demand, and admins can cap overage at $0.

The pool is small on purpose. In April 2026, Computerworld reported the add-on at $15 per user per month for 100 requests. Now the entry price is zero and the marginal price is higher. Asana’s CFO said the company is seeding usage deliberately. It accepted a $1.2 million revenue timing hit and about 150 basis points of gross margin pressure in the second half to do it. AI Studio and AI Teammates were about 25% of net new ARR in the quarter.

4Asana picks the model, and keeps that choice to itself

Anthropic’s customer page says AI Teammates run on Claude Opus 4.6 in a multi-agent setup built on Claude Managed Agents. Asana’s FAQ lists five model partners, with Google Gemini added in July 2026 and open-weight models through Fireworks.ai in September 2026, the month Teammates went into every plan. Asana’s CEO told investors that “behind the scenes, Asana is going to select and optimize the appropriate model.” AI Studio rules already offer a “Let AI decide” model setting.

My read: once Asana charges per finished request, every model call is Asana’s cost, so routing cheaper models where they are good enough is how the margin comes back. Asana told investors it expects gross margin to recover through cost optimization. The cost for buyers is that answer quality can move under you without a release note. Asana has also completed its AI testing only in English.

What to watch#

Two audiences in one request
The Teammate reads from the overlap of your access and its own, then posts where everyone on the task can read. Before you ask, check who is on the task.
A request is Asana’s call
A Teammate that is a collaborator on a task reads every new comment, decides whether it was meant for it, and bills a request if it starts work. Watch the admin usage dashboard, which alerts at 65%, 85% and 100% of the monthly pool.
No stop, undo or retry contract
Disconnecting an app is a settings change. Stopping a run, reversing a write in Gmail or Google Docs, and avoiding duplicates on a retry are not documented. Forgetting a memory does not remove comments the Teammate already posted.
A temporary bypass
Adding a task to another project skips approval under a flag Asana labels temporary. Until that changes, a Teammate can move a task into a project with a wider audience without asking.

What it means for your team#

What to decide before you ship an agent like Asana AI Teammates.

Security
Decide which apps Teammates may use through App management, since every app is allowed by default. One authorization covers all of a person’s Teammates, and each connection carries that person’s full Gmail, Drive or Slack access.
Product
Decide where the agent’s output lands before deciding what it may read. If a task’s collaborators are wider than its sources, have the Teammate reply in a narrower task or a document with its own sharing.
Finance
Budget in requests, since seats no longer set the AI bill. A 200-person Advanced plan includes 50 requests a month for the whole company and then $0.50 each, so set the overage cap and the alert owner on day one.
Platform
Build the undo and the duplicate check yourself for anything a Teammate writes through MCP or a connected app. Asana documents approval before the write and nothing after it.

Steal this

Give the agent a login with a new hire’s permissions, and answer only from the overlap.
Check who will read the agent’s reply separately from who may read its sources.
Charge for finished work, and make coaching free so people keep teaching the agent.

Reference#

The evidence behind this teardown: recordings, sessions, what Asana AI Teammates gets right and wrong, and every source.

Walkthrough · 4 frames

From an assigned brief to the Teammate’s access and memory#

Frames from the recording in Asana’s forum post “Behind the build: a hands-on AI Teammates walkthrough from Asana’s CPO”. A vendor recording, not a live test; the post gives no recording date.

Step 1 of 4: The brief goes to Campaign Brief Writer
Image: Asana recording · 1:50
1. The task’s assignee is Campaign Brief Writer, labeled “AI Teammate”.
2. The description lists the sources: 2024 Summer Campaign Performance, 2026 Product Launch Calendar and the Campaign Brief Template.
3. The task has two collaborators so far; Asana says Teammate comments are visible to everyone with access to the task.
Step 2 of 4: The Teammate reports back in comments
Image: Asana recording · 2:35
1. The Teammate proposes three reviewers from Product and Marketing, and the requester replies “Yes thank you”.
2. The Teammate links the Solano Summer Campaign Brief document and reports an approval task, both inside the comments.
3. A collaborator asks for the feedback to be incorporated, and the Teammate’s change list lands where every collaborator can read it.
Step 3 of 4: The requester approves in a comment
Image: Asana recording · 2:55
1. The requester tags the Teammate and writes “Approved — let’s move into creative development.”
2. The comment doesn’t tie the approval to a version of the Solano Summer Campaign Brief document.
3. The frame doesn’t show whether the Approve Campaign Brief task itself was completed.
Step 4 of 4: The Teammate’s access, rules and memory
Image: Asana recording · 3:24
1. The Teammate has Viewer access to the private 2026 Product Launch Calendar; the frames don’t show which reviewers can open it.
2. All three memory cards cite their sources, and each cites the private 2026 Product Launch Calendar.
3. Behavior guidance holds the Teammate’s written rules, separate from what the Teammate can access.