What's changed: Created Associate Google Workspace Administrator Chapter 2 (Domain 2 "Core services": configuring Gmail/Drive/Calendar/Meet = routing/sharing scope/resources/recording-participant control; service on/off and additional apps = on/off per OU/group, allow/block Marketplace/connected apps, API access management).
2.1Configuring core services (Gmail, Drive, Calendar, Meet)
Understand configuring core services per OU/group: Gmail routing and compliance (routing rules, attachment limits), Drive sharing and storage, Calendar resources (rooms) and sharing, and Meet meeting policies (recording, participant controls).
The value of Google Workspace lies in core services like Gmail, Drive, Calendar, and Meet. Administrators configure each service to match organizational policy. Many settings can be differentiated per OU or group.
2.1.1Gmail and Drive
In Gmail, configure routing/receiving rules to send matching mail to another destination, content and attachment restrictions for compliance, and spam/phishing defenses. In Drive, manage sharing scope (whether sharing outside the org is allowed) and team-owned shared drives. Map "forward/control mail by condition = Gmail routing" and "control file sharing in the org = Drive sharing settings."
2.1.2Calendar and Meet
In Calendar, register resources such as rooms so they can be booked, and manage event sharing scope (how free/busy is visible). In Meet, set recording permission, participant controls (external participants, host management), and quality-related settings per OU/group. Map "book a room = Calendar resource" and "recording/participant control = Meet policy."
Common: requirement → setting. E.g., "conditionally route mail to another destination" = Gmail routing; "restrict external file sharing" = Drive sharing settings; "make rooms bookable" = Calendar resources; "allow/deny recording only for a certain OU" = Meet policy (per OU).
Watch the mix-ups: (1) Many settings can be differentiated per OU/group (not always org-wide). (2) Drive sharing scope ties directly to data-protection policy. (3) Meet recording permission can be controlled per OU.
2.1.3Section summary
- Gmail = routing/receiving rules and content/attachment restrictions
- Drive = sharing scope (external sharing) and shared drives
- Calendar = resources (rooms) and sharing; Meet = recording/participant control, per OU/group
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. To forward/control mail matching certain conditions to another destination, what do you set in Gmail?
Q2. To control whether files can be shared outside the org, what do you set in Drive?
Q3. To make rooms bookable, what do you register in Calendar?
Q4. To allow/deny Meet recording only for a certain department, which best fits?
Q5. Which is a common characteristic of many core-service settings?
Q6. For team co-ownership where files remain with the org as members change, what do you use in Drive?