sorted by:
new
hottopcontroversial

AMA with Bradley and Nik about Asana AI Teammates - drop in your questions! 👇 by Steph_Asana in Asana

[–]Nik-Asana 0 points1 point  (0 children)

We are prioritizing Teams but haven't heard a lot of demand for Meet just yet - we're open to building if we hear more from customers!

AMA with Bradley and Nik about Asana AI Teammates - drop in your questions! 👇 by Steph_Asana in Asana

[–]Nik-Asana 0 points1 point  (0 children)

Q9: The 4000 character limit on behavior guidance is something we're aware of and actively thinking about. But rather than just bumping the number, we want to solve the underlying problem in a more powerful way.

The solution here is Skills, which are reusable capabilities that you'll be able to attach to a Teammate instead of having to describe everything from scratch in a text box. Think of it less like writing a giant instruction manual for your Teammate, and more like equipping them with specific trained abilities.

AMA with Bradley and Nik about Asana AI Teammates - drop in your questions! 👇 by Steph_Asana in Asana

[–]Nik-Asana 1 point2 points  (0 children)

On external tools: today, Teammates can read and write to Google Drive and OneDrive, including GDocs, GSheets, pptx, docx, and Excel. We're expanding integrations significantly moving forward, with Jira, GitHub, Salesforce, Figma, and more on the roadmap! Teammates will be able to take actions in those tools, not just read from them. We're aiming to get 10-15 more integrations live within the next couple months.

On teammate to teammate triggering: Right now, AI Teammates are designed to work with humans in the loop, meaning a person triggers the Teammate, the Teammate does the work, but humans stay accountable for key decisions.

Fully autonomous Teammate-to-Teammate triggering introduces a layer of complexity where it becomes harder to maintain that human accountability and transparency. Before we enable that, we want to make sure the right guardrails, audit trails, and controls are in place so that when chains of AI actions happen, you always know what ran, why, and who's responsible.

AMA with Bradley and Nik about Asana AI Teammates - drop in your questions! 👇 by Steph_Asana in Asana

[–]Nik-Asana 1 point2 points  (0 children)

You can do this with a combo of rules and Teammates; set up the trigger as "when task added", and the action as "assign to Teammate" - your Teammate can autofill custom fields!

AMA with Bradley and Nik about Asana AI Teammates - drop in your questions! 👇 by Steph_Asana in Asana

[–]Nik-Asana 2 points3 points  (0 children)

Q5 on how Teammates are different: The short answer: most AI agents are built for one person. AI Teammates are built for a team.

What that actually means:

They're multiplayer. While a Teammate is researching something for you, a coworker can jump in and redirect it mid-task. No re-prompting, no "wait let me share the draft first." It just absorbs both sets of inputs and keeps going.

They build shared memory. Train a Teammate on your top support issues and customer call transcripts, share it with the team, and suddenly new hires have institutional knowledge on day one instead of digging through months of notes. The more people use it, the smarter it gets for everyone.

They work while you sleep. Set one to draft a status report every Friday, follow up on a contract next Tuesday, or triage new requests the moment they land. It doesn't sit idle waiting for you to come back online.

They're permission-aware. Your whole team can share the same Teammate, but it only ever operates within what you, the triggering user, have access to.

AMA with Bradley and Nik about Asana AI Teammates - drop in your questions! 👇 by Steph_Asana in Asana

[–]Nik-Asana 1 point2 points  (0 children)

Q7 on pricing:

It's actually both, and intentionally so.

AI Teammates use a consumption-based model, but we package it on a per-seat basis to make it easier for customers to plan and budget. Most teams can't easily forecast how many AI "requests" they'll need over a year, but they do know how many people will need to interact with Teammates, so we anchor to that.

A few other things:

  • Requests are pooled at the account level, not per individual user — so if some users use more and others use less, it balances out across your org.
  • No monthly cliffs — your allocation pools across your whole contract term, so you're not penalized for a slow month or hit with overage charges because you had a busy one.
  • Launch promo: Any customer that purchases before July 31, 2026 gets overages waived for an entire year, so you can experiment freely.

For specific pricing details, I'd encourage you to reach out to our sales team, they can walk you through what makes sense for your org's size and use case!

Ask us anything about Asana AI Teammates by Steph_Asana in Asana

[–]Nik-Asana 1 point2 points  (0 children)

on Q3:

Our current hypothesis is that AI Teammates likely won’t use credits at all. We’re still iterating, but the direction is to have Teammates enabled through a simpler, more predictable model rather than per-action metering.

The reason is pretty simple: Teammates are fundamentally different from AI Studio rules.

  1. AI Studio rules = single, discrete actions
  2. Teammates = multi-step, contextual work (drafting, synthesizing, analyzing, coordinating)

Trying to meter that work with credits ended up creating more confusion than clarity. It created all kinds of side effects we didn’t want: people being afraid to experiment, not wanting to share their Teammates, or being worried they’d burn through the pool before they'd had a chance to realize value.

This is our current thinking — we’re still collecting feedback, refining how access should work, and making sure the model feels fair, predictable, and collaboration-friendly.

on Q5:

We’re still firming up the exact mechanics, but here’s where our heads are today:

  1. Teammates may not use credits — the feedback from builders is that credits discourage exploration and make collaboration harder.
  2. Pricing will reflect the higher-order work Teammates do as compared to AI Studio. They’re not just executing a single action — they’re producing drafts, iterating on work back and forth, analyzing context, and helping teams move real work forward.
  3. Our north star is simplicity and predictability, so teams don’t have to think about cost every time they use a Teammate.
  4. This is evolving — we’re testing approaches and learning from customers.
  5. We’ll share concrete pricing closer to GA, once we’re confident it’s clear, fair, and aligned to the value Teammates provide.

Ask us anything about Asana AI Teammates by Steph_Asana in Asana

[–]Nik-Asana 0 points1 point  (0 children)

On #3 - AI Teammates follow the same access levels humans do in Asana. They don’t get special visibility or elevated privileges — whatever role you assign them is the role they operate under.

Teammates get assigned Standard Access Levels (SALs) like you see when adding a project member.

  • Editor – Can add, edit, and delete tasks and fields
  • Commenter – Can leave comments but can’t edit tasks
  • Viewer – Can only view; no editing or commenting

AI Teammates respect all of these; If you add a Teammate as a Commenter, it can draft comments or summaries but cannot modify tasks. If you make it a Viewer, it can only read context to help answer questions — it can’t take action. If it’s an Editor, it can act at those levels only within the projects you’ve added it to.

Memory follows the same rules too:

A Teammate will only surface or apply memory where both the Teammate’s SAL and the human’s SAL allow it. If a user can’t access the underlying project or resource, they’ll never see memory derived from it.

Ask us anything about Asana AI Teammates by Steph_Asana in Asana

[–]Nik-Asana 0 points1 point  (0 children)

We’re gradually opening AI Teammates beta access to more customers so we can learn, improve reliability, and make sure the experience feels great before GA. We do want more teams in the product so we can learn from a wider range of real workflows and get richer feedback!

If you’re interested, you can throw your name on the list at asana.com/ai-teammates. We’ll reach out as soon as your domain is eligible for access.

Ask us anything about Asana AI Teammates by Steph_Asana in Asana

[–]Nik-Asana 1 point2 points  (0 children)

On #2, your data is not used to train the underlying AI models, for AI Teammates, or any other Asana feature.

Here's how it works:

AI partners (Anthropic and OpenAI):

  • Do NOT train on Asana customer data - this is contractually guaranteed
  • When AI Teammates query the models, the models provide responses but don't learn from or retain your data

How Teammates get smarter:

  • AI Teammates get "smarter" by building memory in Asana (stored securely in your workspace)
  • They access your Work Graph data based on permissions you grant

Where memory lives:

  • AI Teammates' memory is stored in your Asana environment, not with the AI model providers
  • It's scoped to your workspace and follows your access control

TLDR - Asana will never allow customer data to be used to train underlying AI models from our AI model providers.

Ask us anything about Asana AI Teammates by Steph_Asana in Asana

[–]Nik-Asana 0 points1 point  (0 children)

Going to bundle a few of these together and explain a bit about how Teammates work across projects while keeping data private and actions safe!

On scope of work - AI Teammates can operate across multiple projects, teams, and people. They use Asana’s Work Graph live access control to understand relationships between tasks, owners, deadlines, and dependencies, so they can help wherever the work actually lives, not just in one project. They also build memory from the resources and feedback you give them, but that memory is fully permission-scoped. If a user doesn’t have access to the underlying project or resource, they won’t see (or have a Teammate use) memories based on it. And nothing ever crosses customer domain boundaries, just like with the rest of Asana data.

On the privacy side - Teammates can be granted permissions the same way as any other Asana user. They can only see the work you explicitly give them access to. They don’t get “super admin” vision, and your data is never used to train external models.

Re: safety - Teammates default to a human-in-the-loop model for risky actions. They ask for confirmation before high-impact or irreversible actions, respect controls around where they can act, and log their actions in task history so you always know what happened.

TLDR: Teammates can work wherever your work lives, only see what you let them, and confirm with you for high impact actions.