Profile

Thank you for kicking off this conversation, Amy. This is an exciting topic, and I'm happy to provide some additional information and an offer to connect with my team for those that would like to learn more about Google's work in AI and our offerings for education. Google Bard is an experimental tool ...

Hi all, It's wonderful to hear the different perspectives on this thread. I wanted to chime in and answer Sarah's initial two questions: 1) When we purchase a new stack, I assume that comes to us as a single invoice just for the storage requested. Is this correct? Invoicing is generally managed by ...

Hi Eric, I'm so sorry to hear that this has been your experience. I'll send you an email directly and loop in your Google points of contact. Thank you for your patience and reaching out. If anyone else is looking to connect with the Google for Education team, please send me an email at aswb@google.com. ...

Hi EDUCAUSE Workspace Community, Jean and Allan, thank you for sharing your insights and strategies with the group. Jean, per your message around user notifications, when a user's account is 80%-100% full, in-app notifications will be visible in Drive, Photos, and Drive for Desktop to warn users of disruption ...

Hi EDUCAUSE Workspace for Education Community, The new Workspace for Education storage policy was announced in February of 2021. Since then, we've been partnering with and listening to customers to ensure that we're providing the best resources and support. In a recent Workspace blog post, we announced ...

Thank you for kicking this off, Jay. Hi EDUCAUSE Google Workspace community. My name is Drew, and I lead the Workspace for Education team in North America. If any of you would like to connect with your Google representatives, please send me an email (aswb@google), and I'm happy to loop in the right ...

Hi EDUCAUSE Workspace Community, Thank you for sharing your insights and feedback around this. We apologize for any frustration or confusion this may have caused, and we're working with our internal teams to understand why this happened and how to avoid similar issues moving forward. I'd like to share ...