Book Image

Google Workspace User Guide

By : Balaji Iyer
Book Image

Google Workspace User Guide

By: Balaji Iyer

Overview of this book

Google Workspace has evolved from individual Google services to a suite of apps that improve productivity and promote efficient collaboration in an enterprise organization. This book takes you through the evolution of Google Workspace, features included in each Workspace edition, and various core services, such as Cloud Identity, Gmail, and Calendar. You’ll explore the functionality of each configuration, which will help you make informed decisions for your organization. Later chapters will show you how to implement security configurations that are available at different layers of Workspace and also how Workspace meets essential enterprise compliance needs. You’ll gain a high-level overview of the core services available in Google Workspace, including Google Apps Script, AppSheet, and Google Cloud Platform. Finally, you’ll explore the different tools Google offers when you’re adopting Google Cloud and migrating your data from legacy mail servers or on-premises applications over to cloud servers. By the end of this Google Workspace book, you’ll be able to successfully deploy Google Workspace, configure users, and migrate data, thereby helping with cloud adoption.
Table of Contents (14 chapters)
Part 1: Getting Started – Google Workspace
Part 2: Data Security
Part 3: Data Integrations
Chapter 6: Designing Custom Applications
Part 4: Migrating Data

Configuring OUs in Cloud Identity

Before setting up users, OUs must be configured in Cloud Identity. These help in categorizing users and enabling respective apps for each OU. Apps such as Gmail, Drive, Meet, and Chat can be selectively enabled for the OU, and further security settings within each of these apps can be applied to sub-OUs.

In the previous chapter, we went into detail about subdomains versus secondary domains. Users across multiple domains or subdomains can be set up under any OU.

Root-level or top-level OUs take over the primary domain name. All child OUs will automatically inherit settings defined for the root OU, but these can be changed by overriding the settings.

For example, if the root OU is, administrators can configure sub-OUs with various names such as IT Staff, Executives, and Field Workers. Within these sub-OUs, there can be nested OUs as well. Users are created as leaf nodes in this hierarchical setup. Those users can belong to either...