Google recently announced an open beta of the new Policy API. This new API now means developers can read a number of Google Workspace Admin settings programmatically, including those applied at an OU and group level.
This API provides access to the settings that are part of the recommendations published in CISA’s Google Workspace secure configuration baseline, with plans to increase the coverage and functionality of the API.
Additionally, GAM7, the recent merge of GAM and GAM-ADV, has been updated with the ability to read policy data, further streamlining policy management tasks.
In 2022, we made it easy to seamlessly access popular Education Technology tools directly in Google Classroom. We partnered with 20+ EdTech companies, including Kahoot!, Pear Deck, IXL, ReadWorks, and Nearpod, to build Google Classroom add-ons. These new integrations let educators and students easily find, use, and grade great content in their favorite EdTech tools without having to navigate to external websites and apps.
Today, we’re excited to make Classroom add-ons generally available to all developers.
Given the number of Apps Script users in EDU today’s announcement the Google Classroom add-ons now generally available for anyone to publish is probably welcome news. Whilst Google Classroom add-ons have been around for a couple of years they have historically only been created by a select few of Google partners.
Before jumping in something key to keep in mind is that while Apps Script offers a low-entry approach for most Workspace add-ons, Classroom add-ons require more technical expertise. They involve building a web application and integrating it with Classroom’s functionalities using the Google Workspace Marketplace SDK. Proficiency in web development languages like Python, Java, or Node.js is recommended and Google have published some example implementations for Python, Java and Node.js.
Whilst there are differences there are overlaps. For example like Workspace and Editor Add-ons you will need to create a Google Cloud project to publish to the Google Workspace Marketplace. As part of this you’ll have to also provide key information such as terms and conditions as well as going through the OAuth verification process.
The Google Developer documentation and other resources are linked from the source announcement.
To bring the power of AppSheet to more users, AppSheet Core licenses will now be included for the following Google Workspace editions…
By including AppSheet Core licenses in more Google Workspace editions, the power of AppSheet is accessible to more users. Further, Admins will have the security features they need to ensure their users are using AppSheet appropriately in their organization.
Previously AppSheet Core licenses were included with Workspace Enterprise Plus, Enterprise Essentials Plus, and Education Plus users. Google have recently announced that AppSheet Core licenses will also be included in the following Google Workspace editions:
Business Starter, Standard, and Plus
Enterprise Starter and Standard
Frontline Starter and Standard
Non-profits
Education Standard
This is great news for Google Workspace users as AppSheet includes a number of out-of-the box features which already integrate into other Workspace products, like dynamic emails, Google Chat and Google Apps Script integration.
Along with the expansion of Workspace editions getting AppSheet Core, is the news that Admins will have basic security controls which can disable external usage of AppSheet apps.
Looking at the associated new security settings support page, it was interesting to see that turning on AppSheet Core security will disable ‘external integration through the app API’:
Finally a little plug. If you are interested in AppSheet and would like to find out about training and support services get in touch. At CTS, where I work, we’ve a growing reputation in both products built using AppSheet as well as helping you get the most from the platform in your organisation.
Many of our customers already take advantage of the Drive Labels capabilities to classify content and implement policies on their Drive files for governance and Data Loss Prevention.
Today, we’re happy to announce a highly requested update that will enable you to programmatically manage labels at scale via Drive APIs.
Google Workspace devs might be interested in this update to the Drive Labels API which enables additional functionality. As noted in the source post:
The new Drive Labels API supports reading Drive Label taxonomies. New functionality in the Drive API can be used to apply labels, set fields on files, and find files by label metadata. As a whole, these new API features enable numerous use cases including, bulk-classification, Apps Script driven workflows, third-party integrations, and other organizing and finding needs.
The post includes links to a number of useful resources including reference documentation.
The Google Forms API provides programmatic access for managing Google Forms and acting on responses— empowering developers to build powerful integrations on top of Forms.
Available to all Google Workspace customers, as well as legacy G Suite Basic and Business customers and users with personal Google Accounts
We’ve shared a couple of updates on the new Google Forms API previously here on Apps Script Pulse. The good news is the Forms API is now out of beta and available for testing and deployment. For Google Apps Script devs I’m sure you are thinking ‘but we can use the Forms Service?’ You can and likely in most instances to be the first port of call, but the new API brings some additional functionality not supported in Forms Service, in particular, a trigger when a Google Form is edited.
The Google Forms API is now rolling out as an Open Beta which means developers who are part of our Early Adopter Program can make their integrations available to the public. We’ll no longer require individual end-user accounts to be allowlisted. … Developers can apply to join our Early Adopter Program and begin developing using the Google Forms API by filling out this form.
In other Google Workspace news the new Google Forms API continues it’s journey to general availability with the announcement of the open beta. Just as the other Google Workspace REST APIs can be useful to Google Apps Script developers it’s useful to keep an eye on what is possible in the Forms API.
Google Workplace Add-ons are now available for Google Docs, Sheets, and Slides. Google Workspace Add-ons are already available for Calendar, Gmail, and Google Drive.
There have been Editor Add-ons for a number of years, with Google Workspace Add-ons developers can tap into a new integrated user experience. One of the main differences with Workspace Add-ons is the use of the Card service rather than custom HTML (HTMLService). The benefit of switching to a Card service is cross platform support including integration into Google’s Workspace mobile apps.
Follow the link to the source post for links to all the relevant developer documentation.
