Difference between Google Workspace G Suite Organisational Units OU and Customize Access Groups

In this video, I'll explain to you the difference between the organisational unit and access group of Google Workspace. Now you've started your cloud journey with Google. It’s time to get your Google Workspace or G Suite for Education set up and running!

Useful Links Customize access to services using access groups https://support.google.com/a/answer/9050643

How the organisational structure works https://support.google.com/a/answer/4352075?hl=en

About user and device policies https://support.google.com/a/answer/182433

Turn a service on or off for Google Workspace users https://support.google.com/a/answer/182442?hl=en

Ways to Create Group https://support.google.com/a/answer/33343?hl=en#differences&adminconsole&create-new&create-classic&directory&api&gcp&sending&target_audiences

Creating a mailing list https://support.google.com/a/answer/9400082?hl=en

Organzational Policy FAQ https://support.google.com/a/answer/4390551?hl=en&ref_topic=4390186

First of all, what is an organisational unit? An organizational unit, OU, in short, is simply a group that an administrator can create in the Google Workspace Admin console to apply settings to a specific set of users. If you’re an admin at a decently sized domain you may need to have several organization units set up within your Google Workspace account. Visually, OU is quite similar to your actual "Business Organisation Structure". I'll explain it to you with examples in a moment.

As mentioned earlier, the OU determines which service a department may access and which services are off-limits. If you set up your users' accounts in their related organizational units, you can turn a service on or off, enforce policies, by the department.

In this example, you can clearly see that the OU is very similar to your "Business or School Organizational Structure". The admin placed all the teacher accounts in the teachers OU. This way, he can switch on or off the service to the teachers without affecting the other part of the organisation.

By default, the Child OU inherits the settings from the parent. For example, if the admin switches on or off service at staff OU, the management and teachers OUs will inherit the settings from the staff's OU.

Although each child inherits settings from its parent, these settings can be customised. The important thing, I want to highlight is that changing a setting at a higher level changes the setting for all sub-organisations that inherit that setting. However, custom settings remain unchanged. Therefore, the Admin should always check the effectiveness of higher-level policies on children OUs.

What is an access Group? Access Group lets you control access for specific users without changing your organizational structure. You can turn on services for a group of users rather t ... https://www.youtube.com/watch?v=6K2ADC_CD1U