Asana Gov Use Requirements and Limitations • Asana

·Asana Gov Use Requirements and Limitations

·These Asana Gov Use Requirements and Limitations apply to Customer's use of Asana Gov and are incorporated by reference into the applicable subscription agreement governing the use of the Asana Gov Service, and Asana's Product-Specific Terms (collectively, the "Agreement"). All capitalized terms not defined herein have the same meanings given to them in the Agreement.

11. Obtaining Asana Gov

·Customers must agree to Asana's Subscriber Terms, or enter into a governing agreement with Asana that include terms substantially similar to the Subscriber Term, which incorporate our Product-Specific Terms and these Asana Gov Use Requirements and Limitations . Customers retain the primary responsibility for ensuring compliance with applicable federal rules and regulations. Asana will satisfy its obligations primarily by empowering customers with the necessary tools to maintain compliance.

·To purchase Asana Gov and any related add-on products, Customers should contact a member of Asana's Sales Team or an Asana Channel Partner. The Sales Team or Channel Partner will assist Customers with an Order Form, which will incorporate the Agreement by reference.

22. Feature Enablement Requirements

·For U.S. Federal Government customers:

·Before submitting any Federal Data or sensitive data into the Asana's Services you must:

• ·purchase Asana Gov;
• ·enable the appropriate settings within your admin console as further detailed in the Documentation; and
• ·enable or keep enabled multifactor authentication, SSO, or Google Authentication for all of your End Users.

·Please note, Asana Gov is a separate and distinct offering from Asana's commercial product, some features or functionalities available in Asana's commercial product may not be available or may be disabled by default. You may enable such features or functionalities, but you do so at your own risk. These features include, but are not limited to, some Asana AI tools, integrations with certain third-party services, and personal access tokens. These limitations may be updated from time to time, and more information is available in Asana Gov Help Guide and Asana's FedRAMP Datasheet .

33. Restrictions.

·To ensure your data remains in FedRAMP Authorized environment of the Asana services, you and your End Users:

• ·should not submit Federal Data to any services outside of the Asana Gov Service. For the avoidance of doubt, specific technical and security measures only available in the Asana Gov Service may not be applicable to Federal Data submitted through other Asana services, including but not limited to Asana's Support Services or in connection with the Professional Services (e.g. via email, support portal or tickets, chat bots, etc.); and
• ·may submit Federal Data into free trial versions of the Asana Gov Service subject to any disclaimers provided in the Agreement.

44. Obligations

·You:

• ·are solely responsible for managing you and your End Users' access to Federal Data in the Asana Gov Services;
• ·must ensure that each of your End Users has their own dedicated email domain (unless Asana agrees otherwise in writing). Personal email domains are not permitted;
• ·must ensure that visibility to Federal Data is limited to End Users on a need-to-know basis by using available Asana Gov Services features and functionalities to do so (e.g. private tasks, private projects, etc.); and
• ·are solely responsible for using the Asana APIs and audit log to monitor for unusual activity in your workspace.

55. Asana Gov Free Trials

·Asana may provide free trials with defined time limits for you to evaluate the Asana Gov Service. Please reach out to a member of Asana's Sales Team for more information.

66. Updates

·Asana may update these Asana Gov Use Requirements and Limitations from time to time and shall notify you of these updates upon such update.