Legal
Product-Specific Terms
Last Updated: November 9, 2026
These Asana Product-Specific Terms (“Product-Specific Terms”) form part of the Asana Subscriber Terms, Asana User Terms of Service, or other existing customer agreement between Asana and Customer applicable to use of the Asana Service (the “Agreement”) and apply only to the extent Customer uses the applicable feature, service or product, or exercises the rights, identified below. All capitalized terms not defined in these Product-Specific Terms have the meanings given to them in the Agreement. In the event of any conflict between these Product-Specific Terms and the Agreement, these Product-Specific Terms control. For purposes of these Product-Specific Terms only, “Customer” also refers to users subject to the Asana User Terms of Service.
Asana AI
Pursuant to the terms below, Asana grants Customer a non-exclusive, revocable, non-transferable, limited right to access and use Asana AI in accordance with the Agreement.
Asana AI. As used herein, “Asana AI” means Asana features and functionality of the Services made available to Customer that use artificial intelligence and/or machine learning (“AI/ML”), as further described in the Documentation; “Input” means any prompt, data, text, or other similar content Customer or any End User submits to the Services to be processed by Asana AI; and “Output” means any data, text or similar content generated by Asana AI and returned to Customer or an End User, as applicable, based on Input.
Ownership. Customer Data includes AI Input and AI Output. As between the parties and to the extent permitted by applicable law, Customer retains all right, title, and interest in AI Input and AI Output. Asana retains all right, title, and interest in Asana AI (including improvements and enhancements to Asana AI, along with new products and features).
AI Limitations; Disclaimer. Asana AI uses AI/ML, which generates predictions based on patterns in data. Customer acknowledges the probabilistic nature of AI/ML and that AI/ML can make mistakes. Customer is responsible for evaluating Asana AI and Output for accuracy and suitability for Customer’s use case(s), including, without limitation, by testing, obtaining any relevant approval(s), and employing appropriate human oversight. Asana makes no warranty regarding the accuracy, completeness, or reliability of the Output and disclaims liability for Customer’s use of Asana AI or any omissions or errors therein. If Customer gives AI agents access to its domain, Customer acknowledges that AI agents can make mistakes and take actions that may be unintended or unexpected. Customer is responsible for double-checking the work of all AI agents within its Asana domain, including those offered by Asana and any third party agents Customer introduces, including External Agents and agents acting through an MCP Connection (as defined below).
Obligations. Neither Customer nor its End Users may represent that Output was human-generated. Customer will use Asana AI consistent with any restrictions and obligations applicable to its use of the Services as set forth in the Agreement. Asana uses technology provided by its third-party AI partners in Asana AI; Customer’s use of Asana AI will comply with the applicable third-party AI partner terms and policies available here, which are incorporated herein by reference.
Restrictions. Customer may not use Asana AI for (i) biometric identification or categorization, or emotion recognition; (ii) determining access to, evaluation, or outcomes in education or vocational training; (iii) making or substantially influencing employment decisions, including recruitment, hiring, performance evaluation, or termination; (iv) assessing eligibility for public benefits or services, social services, credit, or insurance; (v) medical diagnostic or treatment decisions or as a medical device; (vi) safety purposes or components of critical infrastructure; (vii) law enforcement, migration, asylum, or border control purposes, including predictive policing and other crime predictions; (viii) administration of justice or democratic processes; (ix) assigning work to humans based on individual behavior or characteristics, (x) evaluating or classifying natural persons based on their social behavior or personal characteristics leading to detrimental or disproportionate treatment (i.e., ‘social scoring’); (xi) deploying subliminal, manipulative, or deceptive techniques, likely causing harm; (xii) exploiting vulnerabilities of individuals, likely causing harm; or (xiii) any other purpose prohibited under the EU AI Act or other applicable law.
Improving Asana AI. Customer’s use of Asana AI does not grant Asana any right or license to use or share Customer Data in a manner that is inconsistent with the Agreement, unless otherwise agreed by Customer. For purposes of clarity, Asana does not use or permit third-party AI partners to use Customer Data to train generative artificial intelligence models used to provide Asana AI.
AI Agents
The following terms apply to Customer’s use of AI agents provided by Asana, such as AI Teammates and Asana Dash (“AI Agent(s)”), including AI Requests that are included in Asana plans, those purchased separately, and those enabled on-demand.
AI Requests. An “AI Request” is the completion of an interaction or series of interactions with an AI Agent as determined by Asana based on the complexity of the interaction or interactions ("AI Requests"). Based on the applicable subscription plan, Asana may provide Customer with AI Requests included with the plan as shown at asana.com/pricing or the Asana Help Center, which will refresh on a monthly basis. Interactions with AI Agents that result in timed-out errors, service failures, or failed requests will not constitute AI Requests for billing purposes. An AI Agent that resolves a ticket in Asana Service Management consumes an AI Resolution rather than an AI Request.
Allocation of AI Requests. AI Requests will be aggregated and can be consumed by any End User during the Subscription Term.
AI Request Exhaustion. If Customer exhausts existing AI Requests before the end of the Subscription Term and (i) does not purchase additional AI Requests, (ii) does not authorize on-demand charges for AI Requests, or (iii) has reached its limit of on-demand AI Requests (as set in the Admin Console), features requiring AI Requests will not be available until additional AI Requests are purchased or Customer authorizes on-demand charges for AI Requests.
AI Request Balances. In the event of a change in the Subscription before the end of the Subscription Term that requires a new allocation of AI Requests via an amendment to an Order Form, any prorated credits or debits are calculated based on usage data that may be subject to reporting delays. As a result, final and accurate balances will be determined and reflected solely on the invoice provided to Customer.
AI Request Expiration. Purchased AI Requests will remain available until the end of Customer’s then-current Subscription Term. All unused AI Requests automatically expire at the end of Customer’s then-current Subscription Term. Expired AI Requests are forfeited, with no refunds or credits and cannot be carried over from one Subscription Term to the next. AI Requests are non-transferable.
On-Demand Billing. If Customer has enabled on-demand billing through the admin console and exceeds the number of AI Requests allocated during the Subscription Term, AI Requests will be charged on an on-demand basis (“On-Demand AI Requests”). Customer consents and agrees that Asana will charge each On-Demand AI Request at the amount shown in the admin console at the time of enablement or local currency equivalent per request, invoiced on a monthly basis or when a minimum threshold is reached.
Model Context Protocol (MCP) and External Agents
The following terms apply to Customer’s use of Asana MCPs, MCP Clients, External MCP Servers, MCP Connections, External Agents, and External Agent Connections in connection with the Services.
Definitions. "Asana MCP(s)" means any Asana-operated Model Context Protocol server through which MCP Clients may access the Services on behalf of End Users. Asana MCPs are part of the Services. "MCP Client(s)" means any application, AI assistant, agent, or other software not provided by Asana, including any AI model it uses, that Customer or an End User connects or instructs to connect to an Asana MCP. "External MCP Server(s)" means any Model Context Protocol server or service operated by Customer or a third party that Customer or an End User connects to the Services. "MCP Connection" means a connection between the Services and an MCP Client or External MCP Server. “External Agent” means an AI agent, AI assistant, or other AI-powered software offered by Customer or a third party that Customer or an End User connects or instructs to connect to the Services (whether through an Asana MCP, an Asana API, in-product functionality, or otherwise). “External Agent Connection” means a connection between the Services and an External Agent.
Scope and Restrictions. The “AI Limitations; Disclaimer” and “Restrictions” subsections of the “Asana AI” section above apply to Customer’s use of Asana MCPs, MCP Clients, External MCP Servers, MCP Connections, External Agents, and External Agent Connections. Customer may not use any of the above to carry out any use restricted under the “Asana AI” section. In addition, Customer may not connect any MCP Client or External Agent to the Services except through in-product functionality, Asana MCP(s), or Asana API(s) in accordance with Asana’s API Terms. Customer will ensure that its and its End Users’ use of MCP Connections and External Agent Connections complies with the Agreement, and will not connect any MCP Clients, External MCP Servers, or External Agents that Customer knows, or reasonably should know, would cause a violation of the Agreement. Customer will not circumvent or attempt to circumvent any limit, condition, safeguard, restriction, or other control imposed by Asana in relation to the Asana MCPs, MCP Clients, External MCP Servers, MCP Connections, External Agents or External Agent Connections.
Third Party Services. MCP Clients, External MCP Servers, and External Agents are Third Party Services under the Agreement. They are not part of the Services or Asana’s subprocessors, and their data processing is governed by their own separate terms and privacy policies. Customer is responsible for complying with the terms and policies applicable to each Third Party Service, including any acceptable use policies. Third Party Services may not be compliant with HIPAA, FedRAMP, Enterprise Key Management, or data residency requirements, and Customer is responsible for evaluating the compatibility of Third Party Services with such requirements. In no event will Asana be responsible for any act or omission on the part of any Third Party Service or its provider.
Authorization and Risks. By establishing an MCP Connection or External Agent Connection, Customer instructs and authorizes Asana to carry out any requests and instructions – including sharing and receiving information and taking actions – transmitted via the connected MCP Client, External MCP Server, or External Agent. Customer represents that it has all rights and consents necessary for each MCP Connection and External Agent Connection. Requests, instructions, confirmations, and actions taken through an MCP Connection or External Agent Connection using an End User's credentials or authorization are deemed to be the actions of that End User and Customer, and Customer is responsible for such actions. Asana has no obligation to verify the authority, accuracy, or appropriateness of any such request, or to detect, prevent, or reverse any action taken through it. Customer is solely responsible for the security, storage, rotation, scoping, and revocation of all credentials, API keys, OAuth tokens and other access artifacts. Customer agrees not to share Asana login credentials with any Third Party Service and will connect Third Party Services only through authorization methods Asana makes available. Customer acknowledges that MCP servers (including Asana MCP(s)), MCP Clients, External Agents, and other AI-powered agents and features can make mistakes and may also be susceptible to prompt injection, tool poisoning, and similar attacks that cause such technology to take actions or disclose data in a manner that is unintended or inconsistent with instructions. Customer is responsible for configuring permissions and human review appropriate to that risk, and Asana is not responsible for damage from such mistakes or attacks except to the extent caused by Asana’s breach of its security obligations under the Agreement.
Modification or Suspension. Asana may at any time, in its sole discretion and without notice, modify, suspend or disable any MCP Connection or External Agent Connection. Asana may also modify, suspend, or discontinue the Asana MCP or support for MCP Clients, External MCP Servers, or External Agents at any time, in its sole discretion and without notice, which shall not be considered a material decrease in the Services.
Revocation. Customer or its End Users may disconnect any MCP Client, External MCP Server, or External Agent from the Services at any time using the self-service controls described in the Documentation. Any revocation will be prospective only and will not affect the information shared or actions taken prior to revocation.
AI Studio
AI Studio(“AI Studio”) is designed to allow End Users to build rule-based automations that use artificial intelligence (“Smart Workflows”). The following terms apply to Customer’s use of AI Studio, including AI Studio credits that are included in Asana plans, those purchased separately, and those enabled on-demand.
AI Studio Credits. Based on the applicable subscription plan, Asana may provide Customer with AI Studio credits (“AI Studio Credits”) included with the plan for data processing in AI Studio as shown on asana.com/pricing or the Asana Help Center, which will refresh on a monthly basis. AI Studio Credit consumption is calculated by the volume of data, including query, input, and output data, processed through the large language model selected by the End User for a Smart Workflow. Customer is solely responsible for consumption of AI Studio Credits. Any estimate provided regarding consumption of AI Studio Credits is for informational purposes only and it is not a representation or guarantee.
Allocation of AI Studio Credits.
AI Studio Basic and AI Studio Plus. AI Studio Credits will be aggregated and can be consumed by any End User during the Subscription Term.
AI Studio Pro. Customer determines which End Users can consume AI Studio Pro Credits via the admin console
AI Studio Credit Exhaustion. If Customer exhausts existing AI Studio Credits before the end of the Subscription Term and (i) does not purchase additional AI Studio Credits, (ii) does not authorize on-demand charges for AI Studio Credits, or (iii) has reached its limit of on-demand AI Studio Credits (as set in the Admin Console), Smart Workflows requiring AI Studio Credits will cease to run until new AI Studio Credits are purchased or Customer authorizes on-demand charges for AI Studio Credits.
AI Studio Credit Balances. In the event of a change in the Subscription before the end of the Subscription Term that requires a new allocation of AI Studio Credits via an amendment to an Order Form, any prorated credits or debits are calculated based on usage data that may be subject to reporting delays. As a result, final and accurate balances will be determined and reflected solely on the invoice provided to Customer.
AI Studio Credits Expiration. AI Studio Credits will remain available until the end of the Customer's then-current Subscription Term. All unused AI Studio Credits automatically expire at the end of Customer's then-current Subscription Term. Expired AI Studio Credits are forfeited, with no refunds or credits and cannot be carried over from one Subscription Term to the next. AI Studio Credits are non-transferable.
On-Demand Billing. If Customer has enabled on-demand billing through the admin console and exceeds the number of AI Studio Credits during the Subscription Term, additional AI Studio Credits will be charged on an on-demand basis ("On-Demand AI Studio Credits"). Upon exhaustion of AI Studio Credits allocated under the applicable Order Form or plan, Asana will allocate one thousand (1,000) On-Demand AI Studio Credits to Customer, and Customer consents and agrees that Asana will charge the amount shown in the admin console at the time of enablement or local currency equivalent for each group of one thousand (1,000) AI Studio Credits that Asana allocates, invoiced on a monthly basis or when a minimum threshold is reached.
Command by Asana
The following terms apply to the Command by Asana (“Command”) Add-On.
External Agents. Command by Asana (“Command”) allows Customers to connect External Agents and assign them Command tickets. External Agents are Third Party Services under the Agreement and are governed by the “Model Context Protocol (MCP) and External Agents” section above. Customer is responsible for the permissions it grants to External Agents, and for any fees or terms applicable to them. Customer is also responsible for reviewing the work of External Agents, including any code, before relying on or deploying it.
Asana AI Agents. Command includes Chat with Dash, an Asana-native AI Agent that can answer questions and complete tasks. Use of Dash is subject to the “AI Agents” section above, including the terms governing AI Requests.
Eligibility and End User Limits. Command is available as an add-on to Advanced, Enterprise, and Enterprise+ Asana subscription plans. The End User count for Command may not exceed the total End User count under Customer’s existing Asana subscription plan. Customer’s Command Subscription will terminate if its underlying Asana subscription expires, terminates, or is downgraded to an ineligible plan.
Asana Service Management
The following terms apply to the Asana Service Management Enterprise Platform and the Asana Service Management Enterprise Add-On, as well as AI Resolution usage packs that Customer may purchase.
Asana Service Management Enterprise Add-On. The Asana Service Management Enterprise Add-On consists of the Asana Service Management Self-Learning Knowledge Base and the Asana Service Management Enterprise Platform.
End User Limits. The End User count for the Asana Service Management Enterprise Platform may not exceed the total End User count under Customer’s existing Asana subscription plan.
Optional AI Component. The Asana Service Management Enterprise Add-On features an optional AI component, called AI Resolutions, which Customers may purchase separately.
AI Resolution Consumption. An “AI Resolution” means the resolution of a ticket by AI as described in this section. An AI Resolution is consumed when AI resolves a ticket and the submitter either indicates that the ticket is resolved or does not interact with the ticket after receiving a response . An AI Resolution that results in timed-out errors, service failures, or cancellation by the submitter does not constitute an AI Resolution for billing purposes.
AI Resolution Allocation. AI Resolutions will be aggregated and can be consumed by any End User during the Subscription Term.
AI Resolution Expiration. AI Resolutions will remain available until the end of Customer’s then-current Subscription Term. All unused AI Resolutions automatically expire at the end of Customer’s then-current Subscription Term. Expired AI Resolutions are forfeited, with no refunds or credits and cannot be carried over from one Subscription Term to the next. AI Resolutions are non-transferable.
On-Demand Billing. If Customer has enabled on-demand billing through the admin console and exceeds the number of AI Resolutions during the Subscription Term, AI Resolutions will be charged on an on-demand basis ("On-Demand AI Resolution"). Customer consents and agrees that Asana will charge each On-Demand AI Resolution at the amount shown in the admin console at the time of enablement or local currency equivalent, invoiced on a monthly basis or when a minimum threshold is reached.
Asana Client Management
Client Management. Asana's Client Management product ("Client Management") enables Customer to create a portal through which Customer's own clients ("Client Users") may access designated areas of the Services via links provided by Customer. Client Users are not End Users of Customer's Asana subscription and access the Services solely through Customer's portal.
Customer Obligations. Customer is solely responsible for: (a) determining whether Asana AI is appropriate for Customer's use case and for the Client Users Customer grants access to the portal; (b) disclosing to Client Users, prior to their access of the portal, that AI processing may occur in connection with their data, including the nature and purpose of such processing, in a manner sufficient to satisfy all applicable laws and regulations (including, without limitation, data protection, privacy, and AI-specific laws); (c) obtaining any consents, authorizations, or other rights from Client Users required under applicable law for the lawful operation of Asana AI in connection with Client User data; and (d) ensuring that all data submitted by or on behalf of Client Users through the portal is transferred and processed in compliance with applicable law.
Responsibility for Client Users. As between Asana and Customer, Customer is solely responsible for Client Users' access to and use of the portal, including any obligations arising from applicable law in connection with that access. Asana makes no representations or warranties to Client Users relating to the Services or Asana AI.
AI Meetings
AI Meetings. AI Meetings enables End Users to capture audio, generate transcripts, and produce AI-generated summaries and action items from meetings.
AI Consumption. AI Meetings uses AI Requests when an End User records and transcribes a meeting and generates a meeting summary and action items. Actions that result in timed-out errors, service failures, or failed requests will not constitute AI Requests for billing purposes. Terms that govern allocation, exhaustion, calculation, and expiration of AI Requests in the section “AI Agent(s)” apply to AI Requests in AI Meetings.
Consent for Recording. Customer agrees and understands that it is the responsibility of Customer’s End Users to ensure all other participants in any meeting have received all required notices and provided all required consents under applicable law — including applicable federal, state, and local wiretapping, eavesdropping, and recording laws — before any recording or transcription is initiated. In jurisdictions requiring the consent of all parties to a communication prior to recording, Customer shall ensure that its End Users do not initiate recording or transcription using AI Meetings where any participant has withheld or withdrawn consent.
Customer Obligations. Customer is responsible for: (a) establishing and communicating to End Users policies governing use of AI Meetings, including applicable consent and notice requirements; (b) ensuring End Users comply with all applicable laws when using AI Meetings; and (c) ensuring that all data processed in connection with AI Meetings is transferred and processed in compliance with applicable law.
Enterprise+ Unbundling Add-Ons
Permissions Management Add-On
The quantity of Customer’s Add-On Product End Users must equal Customer’s Asana Enterprise Subscription End Users. If Customer increases the number of Asana Enterprise Subscription End Users, Asana will invoice Customer for both the increase in Asana Enterprise Subscription End Users and Add-On Product End Users in accordance with the terms of the Agreement.
Data Residency
Customer will - after migration from an AWS-operated data center in the United States - have its Organization’s Customer Data hosted in an AWS-operated data center in the location listed in the Data Residency SKU listed on the applicable Order Form. As an exception to the foregoing, Customer acknowledges and agrees that the following types of Customer Data shall remain in an AWS-operated data center in the United States: profile information submitted by End Users including email address as well as the organizations to which such End Users have access. Due to Asana’s infrastructural setup, the migrations will happen for the Customer’s entire organization and any of its End Users. For further information, visit one of the following links applicable to Customer’s location:
Enterprise Key Management Add-On
For use of the EKM Add-On, Customer must set up AWS KMS keys in Customer’s own AWS account. More information is provided here.
Customer acknowledges and agrees that some features and elements of the Services are not compatible with EKM and as such will remain unencrypted. These include the following features, which may be updated from time to time within the Documentation
A. Third Party Services, and related metadata
B. Profile images; and
C. Videos created within the Services.
Customer acknowledges and agrees that the following elements of the Services are shared unencrypted with Asana subprocessors to enable provisioning of the Services:
A. End Users’ names and email addresses
B. Team names
The quantity of Customer’s EKM End Users must equal the Customer’s Asana Enterprise Subscription End Users. If Customer increases the number of Asana Enterprise Subscription End Users, Asana will invoice Customer for both the increase in Asana Enterprise Subscription End Users and EKM End Users in accordance with the terms of the Agreement. The two Subscriptions will be billed together under the name “Asana Enterprise" in invoices to Customer.
Compliance Management Add-On
An active, organization-wide Asana Enterprise Subscription is required to purchase access to the Compliance Management Enterprise Add-On. For the avoidance of doubt, Customer must upgrade any applicable existing workspace(s) or existing divisions(s) into an organization-wide Asana Enterprise Subscription in order to purchase access to such organization-wide Add-On Product.
An equal quantity of Compliance Management Add-On Product End Users to Asana Enterprise Subscription End Users must be purchased and maintained. If Customer increases the number of Asana Enterprise Subscription End Users, Asana will invoice Customer for both the increase in Asana Enterprise Subscription End Users and Compliance Management Add-On Product End Users in accordance with the terms of the Agreement.
Customer authorizes Asana to automatically charge Customer for the applicable fees on or after the renewal date of the Compliance Management Add-On Product Term unless either party has provided notice to the other party of non-renewal of the Add-On Product at least thirty (30) days prior to the renewal date. If either party provides such notice of nonrenewal of the subscription to the Add-On Product during the Compliance Management Add-On Product Term, Customer may use the Add-On Product until the end of the then current Compliance Management Add-On Product Term, and there shall be no right to a refund or credit of fees for such remaining period of the Compliance Management Enterprise Add-On Product Term.
Either party must provide the other party with written notice at least thirty (30) days prior to the end of the then-current Compliance Management Add-On Product Term if it wishes to not renew the then-current applicable Add-On Product, and Asana will reflect such nonrenewal within Customer’s billable account on the renewal date, if applicable.
Notwithstanding anything to the contrary in the Agreement or any Order Form, (i) a Compliance Management Add-On Product Term cannot continue beyond the end date of the applicable, then-current Asana Enterprise Subscription Term, and (ii) any such Compliance Management Add-On Product Term current as of the end date of the applicable, then-current Asana Enterprise Subscription Term shall co-terminate with the applicable, then current Asana Enterprise Subscription Term.
Asana Gov Services
Asana Gov Services. For SaaS Services provisioned in a FedRAMP authorized environment ("Asana Gov Services"), Customer acknowledges that Asana Gov Services will only meet the standards of an authorized FedRAMP service if Customer complies with the security controls set out in the Asana Gov Use Requirements and Limitations available at https://asana.com/terms/asana-gov. Customer is responsible for performing its own risk analysis and monitoring the Customer Data that is processed by the Asana Gov Services. The Asana Gov Services may not be used to process or store classified data.
The following terms apply to AsanaGov AI Teammates Requests (“Gov AI Requests”) in lieu of the “AI Agent(s)” Section of the Product-Specific Terms, above.
Gov AI Requests. A “Gov AI Request” is the completion of an interaction or series of interactions with an AI Agent as determined by Asana based on the complexity of the interaction or interactions ("Gov AI Requests"). Interactions with AI Agents that result in timed-out errors, service failures, or failed requests will not constitute Gov AI Requests for billing purposes.
Allocation of Gov AI Requests. Gov AI Requests will be aggregated and can be consumed by any End User during the Subscription Term.
Gov AI Request Exhaustion. On-demand billing is not available for Asana Gov Services customers. If Customer exceeds existing Gov AI Requests before the end of the Subscription Term and does not purchase additional Gov AI Requests, Asana reserves the right to calculate the total number of excess Gov AI Requests consumed during the Subscription Term and to invoice Customer for the excess Gov AI Requests on a periodic basis at the same price per request as shown on the Customer’s Gov AI Request order form for the current Subscription Term. Customer agrees to pay for excess Gov AI Requests consumed during the Subscription Term in accordance with the applicable payment terms on the invoice.
Gov AI Request Balances. In the event of a change in the Subscription before the end of the Subscription Term that requires a new allocation of Gov AI Requests via an amendment to an Order Form, any prorated credits or debits are calculated based on usage data that may be subject to reporting delays. As a result, final and accurate balances will be determined and reflected solely on the invoice provided to Customer.
Gov AI Request Expiration. Gov AI Requests will remain available until the end of Customer’s then-current Subscription Term. All unused Gov AI Requests automatically expire at the end of Customer’s then-current Subscription Term. Expired Gov AI Requests are forfeited, with no refunds or credits and cannot be carried over from one Subscription Term to the next. Gov AI Requests are non-transferable.
For further information on the Asana Gov Services, please visit the Asana Gov Help Guide available at https://help.asana.com/s/article/asana-gov?language=en_US.
Service Requests under the EU Data Act
Available here.
Timesheets and Budgets Add-On Terms
Customer retains administrative control over which End Users it provisions or otherwise allows to use Timesheets and Budgets Add-On product. Customer will not allow a Timesheets and Budgets Add-On end user license to be shared by more than one individual End User (except an end user license may be assigned to a new End User replacing an End User who no longer uses the product). Asana reserves the right to calculate the total number of End Users provisioned or using the Timesheets and Budgets Add-On product on a periodic basis, and if such number exceeds Customer’s current plan size, Asana may invoice Customers for the additional increments of End Users on a pro rata basis for the remaining months in Customer’s then-current Subscription Term.
StackAI by Asana
The following terms apply to purchases of StackAI by Asana (SaaS, On-Premise, and Bring-Your-Own-Cloud):
Platform. The StackAI by Asana Platform (“StackAI Platform”) is a no-code platform that allows organizations to build, deploy, and manage custom workflow automations powered by artificial intelligence.
Builders. The StackAI Platform includes “Builders,” defined as an End User with capabilities to create, modify, and manage Projects, as defined below. Each Builder license is assigned to a single individual and may not be shared among multiple individuals.
Projects. The StackAI Platform includes “Projects,” defined as a rule-based automation that uses artificial intelligence to manage work between external systems.
Runs. The StackAI Platform includes “Runs,” defined as the single execution of a project powered by artificial intelligence. All Runs unused at the end of the current month automatically expire. Expired Runs cannot be carried over from one month to the next. Runs are non-transferable.