How to build a CMS with React and Google Sheets

Jessica Cregg

24 Feb, 2021

Launching a website can feel like a landmark moment. It’s the digital age equivalent of hanging an ‘Open For Business’ sign in your window. If your proverbial sign is static and rarely requires updates – for example, if it’s simply intended to communicate basic operating practices like opening hours, contact information and a list of services – then you can likely build a simple site in HTML and CSS, and wrap the project there. But for most businesses, something far more dynamic is required.

As the term implies, a Content Management System, or CMS, is a structure that enables users to model, edit, create and update content on a website without having to hard-code it into the site itself. Many businesses use off-the-shelf CMS tools like WordPress, Joomla, Magento or Squarespace to handle this function.

When it comes to pin-pointing the factors that really make a really good CMS stand out, the most successful out-of-the-box solutions share one common trait – they’re easy to interpret. For any CMS, its success as a product completely relies on how easy it is for teams to create, manage and update logical data structures. The more pain-free this process is, the easier it becomes for teams to create robust content models. That being said, as any engineer will tell you, the implementation of relational databases is in itself its own art form. 

The problem with these out-of-the-box solutions is that they can often include far too many features, cater to completely different levels of tech literacy, and what’s more, can make it far too easy for you to rack up an expensive bill. An alternative option is to build your own custom CMS that’s designed to meet your specific requirements.

While building the thing that you need is often viewed as the scenic route to solving your problem, when tackled the right way, it can turn out to be the quickest solution. An excellent way of streamlining a project with the potential for infinite scope-creep, while putting any information that’s lying dormant in a spreadsheet to good use, is to use Google Sheets as the foundation for your CMS. 

Despite the best efforts of AirTable, Notion and even Smartsheets, there’s a reason why spreadsheets have stood the test of time as a widely accepted file format. Chances are, no matter the skill level or aversion to technology, most people within a business are going to know how to navigate their way around a spreadsheet. 

In the following tutorial, you’ll see how using popular JavaScript tools including the Node.js framework  and React library, you can stand up a dynamic web application built right on top of Google Sheets. We’ll create a Node project to act as a container for our API queries, and then harness React to parse our data, which will then be presented and served to the user via a dynamic front-end. Here we’ll be taking advantage of React’s tendency to abstract away a lot of the internal complexities of our application’s inner workings, along with its reusable components. The latter feature is perfect if you’re building out a broad website with a multitude of pages that you’d like to all have a consistent look and feel. 

For this example, we’ll be using the ‘Meet the Team’ page for a fictional technology enterprise business. If you’d like to use the example data we’re using for the purposes of this demonstration, you’ll find the spreadsheet linked below. 

What you’re essentially going to do is access your spreadsheet as an API, querying it in order to pull out the content for your front-end React page. We’ll be accessing the data from the sheet in JSON format, and then using the dotenv package in order to store the credentials needed to access the information from our Node project. This will parse the information and feed it through to the front-end, presenting it in a far more polished and stylised format. 

First up, let’s use the terminal to generate a new project from which we’ll be working from. Create a new directory for your project by running ‘mkdir’ followed by your project name, and then step into that directory using the ‘cd’ command. To create our Node project we’ll firstly run ‘$ npm init -y’ from the terminal, before creating two additional files we need to get up and running, using the ‘touch’ command. 

One of these is our .env file which will contain any sensitive keys, credentials or variable settings we’ll need in order to access our Sheet. Remember to keep this section in your .gitignore if you decide to share your repository publicly to prevent your keys from being deactivated and your credentials from being stolen. The last step, as illustrated in the code snippet below, is to install a few external packages we’ll be using in our project. We’ve covered off dotenv, and the googlesheetsapi is no surprise. The final one is Express, which we’ll be using as our Node.js framework due to its lightweight nature and its ability to quickly spin up servers.

$ mkdir project-name

$ cd project-name

$ npm init -y

$ touch index.js .env

$ npm i express google-spreadsheet dotenv

Once you’ve installed your external packages, open up your node project in your preferred text editor and initialise your server using the below code snippet: 


const { GoogleSpreadsheet } = require (“google-spreadsheet”)

const { OAuth2Client } = require(‘google-auth-library’);

const express = require(“express”)()

 // process.env global var is injected by Node at runtime

// Represents the state of the sys environment

const p = process.env

 // Set up GET route in Express

express.get(‘/api/team/’, async (request, response) => {

  response.send(“hello world”)


 // Express listener, on port specified in .env file

express.listen(p.PORT, () =>

  console.log(`Express Server currently running on port ${p.PORT}`)


Here, we’re essentially calling the packages which allow us to access the spreadsheets object, and on line six, we’re setting a variable of ‘p’ that creates a shortcut to process.env. Essentially, this will represent the state of our system environment for the application as it starts running. By adding a shortcut, we’ll be able to effectively access the spreadsheets object with far less effort. 

The rest of the program is initialising our express GET route (a.k.a. how we’ll be querying our sheet) and setting up a listen function in place to assist with our build. This will give us a handy prompt as to which port the express server is running on while we’re working to connect our React front-end to the application.    

Lastly, head into your .env file and assign your port number as per below in plain text, “PORT=8000” and hit save. 

Run node index.js from the root in your terminal, and you should see the listen console.log message appear stating which port your server’s currently running on – in this case, it’s port 8000. 

If you head to your browser and access the port that your application is running on, you’ll notice that your GET method is failing. Let’s fix that. 

At the moment, we’ve got our method for querying our data established. We now need to get the data flowing through our server. The next step here is to assemble your Google Spreadsheet with both the headings and the content you’d like your node project and React app to pull through. If you’d like to follow along, feel free to make a copy of the ‘Meet the Team’ spreadsheet we’ve created. 

The first thing you’re going to need to lift is your SPREADSHEET_ID. You can find this by copying the long string (or slug) found in the URL following the /d/. For example, in this case, our slug is “1f7o11-W_NSygxXjex8lU0WZYs8HlN3b0y4Qgg3PX7Yk”. Once you’ve grabbed this string, include it in your .env file under SPREADSHEET_ID. At this stage, your .env file should look a little something like this: 

Next, head to the Google Sheets Node.js Quickstart page to enable the Google Sheets API. You’ll need to click the blue ‘Enable’ button before naming your project, selecting ‘Web Server’ and entering your localhost URL when configuring the 0auth values. 

If executed correctly, this step will have enabled the Google Sheets API from your Google Cloud Platform (GCP) account. To confirm that’s happened, simply head over to your GCP console and you’ll spot your project in your profile page. 

To authenticate this exchange of data, we’ll need to generate an API key. This will authorise your app to access your Google Drive, identify your Spreadsheet via the SPREADSHEET_ID, and then perform a GET request to retrieve the data to be parsed and displayed on your React front-end. 

To get hold of your API key, you’ll want to navigate to the credentials section of the GCP console, click blue “+ CREATE CREDENTIALS” and select the “API key” option. 

Once your key’s been generated, copy it and add it into your .env file under API_KEY. 

Perfect! Now let’s initialise and use the key within our code to authenticate our Google Sheets query. In the snippet below, you’ll notice that we’re using the await operator to coincide with the async function initiated at the beginning of the index.js program shown earlier in this tutorial. To view the complete code as a reference, you can head here to review and even clone the repository. 

Now we’ve authorised our sheets object, it’s time to minify the data. This is a process by which we remove any unnecessary, superfluous data from the JSON object, so that we’re left with only the most vital sections of the object which we’ll model within our React front-end. 

Head to the index.js file of the linked repository and you’ll see how we’ve been able to do this. We start off with an empty array, and then we iterate through the rows in the sheet assigning a key corresponding to the column header, and match the value to that of the cell data for that particular row.

If you’re familiar with React, then you’ve more than likely used the package create-react-app which is by far one of Facebook’s greatest gifts to the world of application development. With one command, you’re able to spin up an instance giving you the file structure and most of what you need to get going out of the box. 

The ‘create-react-app’ command generates a locally hosted, single-page React application that requires no configuration in order to get going. When you run the command, create-react-app will run local checks on your target directory, builds your package.json, creates your dependency list and forms the structure of your bundled JS files. 

Let’s kick off this process by running the following at the root of our application:

$ npx create-react-app client

$ cd client

$ npm start

If you run into any problems with the version of npm/npx that you’re running, then the below modified command with an added bit of cache clearance should steer you right: 

$ npm uninstall -g create-react-app && npm i -g npm@latest && sudo npm cache clean -f && npx create-react-app client

If your command has run successfully, you’ll start to see create-react-app install its required packaged and build out the below file structure. 

Lastly, you’ll notice that your application now has two package.json files. We’ll need to make an edit to the scripts section in the root, and then add one line below the ‘private’ section of your client directory. This is so that you can fire everything up with one simple command – the eternal saviour that is npm start. 

In your root:

“start”: “node index.js -ignore ‘./client’ “

And in your client: 

“proxy”: “http://localhost:8000

Now with one run of npm start you’ll be met with your React front-end pulling through information from your Google Sheets CMS. 

If you check out the back-end server (running on port 8000) in your browser, you’ll be met with a JSON object displaying your CMS data in its raw, unformatted form. 

But, more importantly for the many stakeholders eager to access your newly-built site, here’s what you’ll see displayed on the front-end. 

What was once entries on a spreadsheet, is now a fully-formatted, somewhat shiny React web app, ready to be deployed through your favourite hosting service. The great thing about this solution is that it can be incorporated into your wider React-based application, and styled using one of many free themes and templates out there, meaning that your final output can actually scale with you. There you have it – yet another reason to love spreadsheets.

Intel joins forces with Google Cloud for 5G edge services

Bobby Hellard

24 Feb, 2021

Intel and Google Cloud have announced a partnership that will see the two firms develop integrated services for network providers to develop 5G innovations across various platforms.

The collaboration is another step towards Intel’s goal to develop 5G networks with software-defined infrastructures and further evidence of Google Cloud’s ambitions in the 5G arena.

Telecom-based cloud architectures and integrated services from both Intel and Google Ccloud will help to accelerate scalable network and edge deployments, particularly with multi-cloud architectures. These are thought to be critical in achieving the full potential of 5G, edge computing and AI across many industries, such as manufacturing, retail and healthcare.

The partnership will focus on three areas, the first of which will be to aid the acceleration of Virtualised RAN (vRAN) and Open Radio Access Networks (ORAN) with infrastructure and hardware support. There will also be a Network Functions Validation lab to support vendors in testing, optimising, and validating their core network functions that run on Google Cloud’s Anthos for Telecom platform. The lab environment will also expand to help customers conceive, plan, and validate their 5G and edge application strategies.

The partnership also includes edge services developed with Intel’s compute-optimisation technology and blueprints to accelerate edge transformation in certain industries.

“The next wave of network transformation is fueled by 5G and is driving a rapid transition to cloud-native technologies,” said Dan Rodriguez, Intel corporate vice president and general manager of the network platforms group.

“As communications service providers build out their 5G network infrastructure, our efforts with Google Cloud and the broader ecosystem will help them deliver agile, scalable solutions for emerging 5G and edge use cases.”

Google Cloud has been very active in this space. The firm recently announced an initiative to deliver more than 200 partner applications to the edge via its network and 5G service.

VMware patches critical ESXi and vSphere Client vulnerabilities

Keumars Afifi-Sabet

24 Feb, 2021

VMware has fixed three critically-rated flaws across its virtualisation products that could be exploited by hackers to conduct remote code execution attacks against enterprise systems.

The firm has issued updates for three flaws present across its VMware ESXi bare-metal hypervisor and vSphere Client virtual infrastructure management platform, including a severe bug rated 9.8 out of ten on the CVSS scale.

This vulnerability, tracked as CVE-2021-21972, is embedded in a vCenter Server plugin in the vSphere Client. Attackers with network access to port 443 may exploit this to execute commands with unrestricted privileges on the underlying operating system that hosts vCenter Server.

Also patched is CVE-2021-21974, which is a heap buffer overflow vulnerability in the OpenSLP component of ESXi and is also rated a severe 8.8. Cyber criminals lying dormant within the same network segment as ESXi, also with access to port 427, may trigger the issue in OpenSLP which could also result in remote code execution. 

Finally, CVE-2021-21973 is a server-side request forgery (SSRF) flaw in vSphere Client which has arisen due to improper validation of URLs in a vCenter Server plugin. This is not as severe as the other two bugs, having only been rated 5.3, but can also be exploited by those with access to port 443 to leak information. 

There are workarounds that users can deploy for both CVE-2021-21972 and CVE-2021-21973 that are detailed here until a fix is deployed by the system administrator. 

Users can patch these flaws, however, by updating the products to the most recent versions. These include 7.0 U1c, 6.7U3I and 6.5 U3n of vCenter Server, 4.2 and of Cloud Foundation, as well as ESXi70U1c-17325551, ESXi670-202102401-SG and ESXi650-202102101-SG of ESXi.

These vulnerabilities were privately brought to the attention of VMware and customers are urged to patch their systems immediately.

Red Hat closes purchase of multi-cloud container security firm StackRox

Rene Millman

24 Feb, 2021

Red Hat has finalised its acquisition of container security company StackRox. 

StackRox’s Kubernetes-native security technology will enable Red Hat customers to build, deploy, and secure applications across multiple hybrid clouds.

In a blog post, Ashesh Badani, senior vice president of cloud platforms at Red Hat, said over the past several years, the company has “paid close attention to how our customers are securing their workloads, as well as the growing importance of GitOps to organisations.”

“Both of these have reinforced how critically important it is for security to “shift left” – integrated within every part of the development and deployment lifecycle and not treated as an afterthought,” Badani said.

Badani said the acquisition would allow Red Hat to add security into container build and CI/CD processes. 

“This helps to more efficiently identify and address issues earlier in the development cycle while providing more cohesive security up and down the entire IT stack and throughout the application lifecycle.”

He added the company’s software provides visibility and consistency across all Kubernetes clusters, helping reduce the time and effort needed to implement security while streamlining security analysis, investigation, and remediation.

“StackRox helps to simplify DevSecOps, and by integrating this technology into Red Hat OpenShift, we hope to enable users to enhance cloud-native application security across every IT footprint,” added Badani. Red Hat initially announced the acquisition in January. The terms of the deal were not disclosed.

In the previous announcement, Red Hat CEO Paul Cormier said securing Kubernetes workloads and infrastructure “cannot be done in a piecemeal manner; security must be an integrated part of every deployment, not an afterthought.”

Red Hat said it would open source StackRox’s technology post-acquisition and continue supporting the KubeLinter community and new communities as Red Hat works to open source StackRox’s offerings. 

KubeLinter is an open-source project StackRox started in October 2020 that analyses Kubernetes YAML files and Helm charts for correct configurations, focusing on enabling production readiness and security earlier in the development process.

StackRox will continue supporting multiple Kubernetes platforms, including Amazon Elastic Kubernetes Service (EKS), Microsoft Azure Kubernetes Service (AKS), and Google Kubernetes Engine (GKE).

Kamal Shah, CEO of StackRox, said the deal was “a tremendous validation of our innovative approach to container and Kubernetes security.”

Mindtree achieves Google Cloud partner status

Bobby Hellard

23 Feb, 2021

Mindtree has announced it has achieved the Application Development Partner Specialisation in Google Cloud’s Partner Advantage Programme. 

The ‘specialisation’ is an acknowledgement of the cloud firm’s expertise and success in building apps and services using the Google Cloud Platform.

Mindtree is an Indian-based tech with offices in Banglore and the US. The firm provides services for outsourcing, data analytics, e-commerce, mobile applications and cloud migrations. 

Google Cloud’s Partner Advantage Programme is designed to provide its customers with access to qualified companies that have demonstrated technical expertise and is designed for firms that show particular success in specialised service areas. For Mindtree, that specialism is in driving digital transformations with cloud migrations and application adoption. 

“Mindtree is committed to helping enterprises grow and scale their business leveraging Google Cloud’s world-class infrastructure and robust set of cloud solutions,” said Radhakrishnan Rajagopalan, the global head of customer success, data and intelligence at Mindtree.

“This recognition instils further confidence in enterprises seeking to migrate their legacy applications and workloads onto Google Cloud that Mindtree can effectively help an organisation drive their cloud adoption initiatives forward.”

Through its collaboration with Google Cloud, Mindtree has boosted its status as cloud migration and digital transformation specialists. For Google, it is further evidence of its cloud strategy to priorities migration and analytical services as it looks to cement its place as the third-biggest cloud provider. 

While they cannot match the sheer breadth of services offered by AWS, other providers like Google and IBM have taken different approaches and sought to specialise in areas of cloud computing,

In 2020, Google Cloud acquired a number of analytical firms and also migration specialists, such as Cornerstone Technologies and Looker. In May 2020, Google also announced that Splunk services were available in beta, with a full rollout later in the year. That partnership was also aimed at providing fast and reliable analytical services to Google Cloud customers. 

IBM reportedly mulls sale of Watson Health business

Bobby Hellard

22 Feb, 2021

IBM is reportedly considering a sale of Watson Health, its artificial intelligence-based medical data service, in order to further streamline its business. 

Talks are at an early stage, according to sources cited in The Wall Street Journal, and the tech giant is thought to be exploring all options.

The sale of Watson Health would be another significant change to IBM’s business under CEO Arvind Krishna. He has yet to complete his first full year in the role but has already overseen multiple acquisitions, including cloud monitoring service Instana and Salesforce consultancy 7Summits.

The company is also in the process of splitting its business in two, which will see its managed infrastructure services unit spun off into a separate entity with the IBM brand focusing on cloud computing.

It’s part of a wider strategy to gain market share in the hybrid cloud market, following the company’s $34bn acquisition of Red Hat in 2019. However, going forward, it appears that Watson Health isn’t part of those plans. The WSJ suggests the tech giant may still continue running the service, but it is in the early stages of pursuing a deal. The company is thought to be exploring a range of options from a sale to a merger with a ‘blank-check’ company. 

IT Pro has approached IBM for confirmation but had not received a response at the time of publication.

Watson Health helps medical providers manage and process data and it generates around $1 billion annually, but it isn’t thought to be profitable as yet. The service was launched with high expectations for revolutionising healthcare with artificial intelligence, with IBM aiming to speed up diagnoses for cancer and other serious conditions. 

However, Watson hasn’t seen much success in the healthcare sector, the WSJ notes, “in part because physicians were hesitant to adopt artificial intelligence”. This lead to IBM laying off a percentage of its Watson Health workforce back in 2018. 

Dropbox takes $400m hit after move to sublease office space

Bobby Hellard

19 Feb, 2021

Cloud storage firm Dropbox has reported a ‘one-off’ loss of $398.2 million in its fourth-quarter report, due to its decision to sublease most its office space as part of a remote work strategy.

The company announced in October that it would be shifting all of its employees to permanent remote work, with the company only using a small portion of its office space for occasional in-person collaboration. As a result, Dropbox then moved to sublease the rest of its space to the market.

The cloud firm, which has leases in San Francisco, Seattle, Austin, and Ireland, noted in its Q4 results that it had incurred impairment charges of $398.2 million after an assessment of its current real estate was downgraded.

“We reassessed our real estate asset groups and estimated the fair value of the office space to be subleased using current market conditions,” the firm noted in its report. “Where the carrying value of the individual asset groups exceeded their fair value, an impairment charge was recognised for the difference. As a result, we recorded total impairment charges of $398.2 million in the fourth quarter of 2020 for right-of-use and other lease-related assets.” 

Although this is regarded as a ‘one-off’ loss, it stands as a significant slump for a company that would have otherwise recorded a strong 2020 performance. In Q1 the firm recorded a profit for the first time since it debuted on the stock market in 2018. With the spread of COVID and the swift change to remote working, the company reported further gains in Q2 and Q3, the latter of which saw net incomes of $32.7 million, almost double the figure reported in the same period a year before ($17.2m).

Dropbox notably decided not to implement the sort of ‘hybrid‘ work strategy that has become popular throughout the industry, where employees can choose to work from home or in the office. The company has maintained that hybrid work arrangements could create two different employee experiences that could ultimately create “barriers to inclusion” and career inequalities.

Instead, it’s ushering in a ‘Virtual First‘ strategy where remote is now the “primary” setup for all of its employees and the day-to-day default for individual work, with the remaining office space being used for occasional collaborative work. 

The firm is also planning to spread further afield with on-demand, collaborative spaces touted for other regions, although these are yet to be announced.

WhatsApp presses ahead with privacy changes despite backlash

Sabina Weston

19 Feb, 2021

WhatsApp has said that a controversial change to its privacy terms that would see the creation of a limited data sharing agreement with its parent company Facebook will now going ahead as planned.

The update to WhatsApp’s privacy policy, which would allow the messaging platform to share some user data with Facebook, was supposed to come into effect on 8 February. However, public backlash prompted WhatsApp to delay the implementation by three months, to 15 May, in order to clarify the details of what the agreement would entail.

Under the new privacy policy, WhatsApp will be able to share limited user data with Facebook and its group firms in order to allow businesses to use the platform for customer service purposes.

However, the company said that this would not affect users’ personal conversations and that it will be up to the user to decide whether they “want to engage with businesses, or not”,  according to a blog post on Thursday. It also added that it will “clearly label chats” in order to make users aware when businesses are managing their conversations using Facebook, and the implementation of the update will first result in the displaying of banners providing additional information on the new terms.

Accepting the new terms will be compulsory in order to continue using the messaging platform, a rule that last month led to millions of users downloading alternative apps such as Telegram and Signal.

As a result. WhatsApp fell from being the eighth most downloaded app in the UK at the start of the year, to the 23rd most downloaded by 12 January, when discussion around the update started gaining momentum.

By contrast, Telegram and Signal gained 25 million and 7.5 million users respectively during the same period, resulting in a brief crash of Signal’s servers. However, it’s unclear how many of these users still have WhatsApp installed, so it’s difficult to assess how many users WhatsApp lost entirely as a result of the move.

WhatsApp acknowledged that it “could have done better” and told users that it will be “doing much more to make [its] voice clear going forward” by using its app’s Status feature to share information on updates and company values directly to its users.

It also addressed the mass uptake in Signal and Telegram downloads, saying that it understands that “some people may check out other apps to see what they have to offer”.

“We’ve seen some of our competitors try to get away with claiming they can’t see people’s messages – if an app doesn’t offer end-to-end encryption by default that means they can read your messages,” the company stated in its blog post. “Other apps say they’re better because they know even less information than WhatsApp. We believe people are looking for apps to be both reliable and safe, even if that requires WhatsApp having some limited data.

“We strive to be thoughtful on the decisions we make and we’ll continue to develop new ways of meeting these responsibilities with less information, not more,” it added.

Microsoft to launch standalone Office 2021 suite

Keumars Afifi-Sabet

19 Feb, 2021

Microsoft will launch a standalone, offline version of its flagship Office productivity suite for users and businesses unwilling to take out a subscription, more than two years after launching Office 2019.

Dubbed Office 2021, this software suite will launch alongside a long-term servicing channel (LTSC) version developed primarily for enterprises, according to the Verge.

Office LTSC will include new features such as support for dark mode, and accessibility improvements, alongside enhancements to core functionality – although the company has refrained from detailing these feature changes.

The announcement follows the company’s hints last year that it would release a ‘perpetual licence’ edition of its productivity suite. This is despite an understanding that Microsoft was seeking to phase out offline variants of Office in light of the huge shift to cloud-based collaboration

Office 2019, for example, was released with a reduced extended support period against that offered in previous offline editions. Users were able to tap into just five years of mainstream support, as opposed to the standard seven years afforded in the past.

Microsoft’s desire to migrate its customers to subscription-based services was also signalled by the launch of Microsoft 365, which encompasses the breadth of its workplace services, including Outlook and Teams.

The imminent launch of Office 2021 and Office LTSC, however, suggests the company understands not all its customers are ready to move to the cloud. 

“It’s just a matter of trying to meet customers where they are,” head of Microsoft 365, Jared Spataro, told the Verge.

“We certainly have a lot of customers that have moved to the cloud over the last 10 months, that’s happened en masse really. At the same time, we definitely have customers who have specific scenarios where they don’t feel like they can move to the cloud.”

Like Office 2019, Office LTSC will only be supported for five years, excluding extended support. Pricing for Office Professional Plus, Office Standard and individual apps will also increase by 10% for commercial customers against Office 2019. Pricing for consumer and small business customers with Office 2021, however, will not change. 

The software giant is planning to release a preview of Office LTSC in April ahead of a full release later this year. Office 2021 will launch at the same time, but won’t be available in preview.

Google introduces new video tools for Meet, Chrome OS

Sabina Weston

18 Feb, 2021

Chrome OS users will now be able to record their screens in meetings, as part of a slew of new features and devices announced by Google.

Although mostly aimed at children and teenagers confined to remote learning as schools remain closed, the new tools are likely to be found useful by a wider audience.

The screen recording tool will be rolled out in March with the latest Chrome OS update, and other new video conferencing features will follow.

For instance, Google Meet is providing teachers with increased control over the virtual classroom, soon giving them the option to end meetings for everyone on the call, which will prevent students from staying on after the teacher has left — including in breakout rooms. They will also be able to prevent interruptions with a new “mute all” tool, which will become available in the next few weeks.

Over the next few months, Google will also be adding a tool which will allow meeting hosts to control when other participants can unmute themselves, as well as provide better access to key moderation controls when using iOS or Android devices.

The newly-announced features are all part of Google’s efforts to increase the safety of underage users, bettering their quality of education as well as preventing major security incidents such as ‘Zoom-bombing’.

To coincide with the release, the company also announced that it will be launching over 40 new Chromebooks, many of which will be 2-in-1 devices that combine the features of laptops and tablets.

The new devices are to be equipped with a stylus, touchscreen, as well as dual-cameras, making it easier for users to take notes, edit videos, record screencasts, and create a range of media, from podcasts to books and illustrations.

Google also announced that it will roll out a range of Chromebooks that can better support students with limited access to a Wi-Fi connection. The “Always Connected” devices will be equipped with LTE connectivity, allowing users to access the internet using their preferred mobile network provider. It’s currently unclear when these devices will become available – IT Pro has sought clarification on this.

Chromebook shipments between October and December 2020 hit an all-time high of 11.2 million shipped units, an increase of 287% from the same quarter in 2019.