[Aug 23, 2025] Associate-Google-Workspace-Administrator Free Exam Questions with Quality Guaranteed [Q47-Q68]

Rate this post

[Aug 23, 2025] Associate-Google-Workspace-Administrator Free Exam Questions with Quality Guaranteed

Associate-Google-Workspace-Administrator Free Exam Files Downloaded Instantly

Google Associate-Google-Workspace-Administrator Exam Syllabus Topics:

Topic	Details
Topic 1	Managing Security Policies and Access Controls: Validating skills of Security Architects and IAM Specialists, this domain enforces password policies, 2SV methods (Authenticator, passkeys), and context-aware access rules. It covers security group management, admin role delegation (super admins), Security Center risk analysis, and third-party app controls (Marketplace allowlists, SAML integration).
Topic 2	Managing Endpoints: This section measures the proficiency of Endpoint Security Engineers and Mobility Managers in applying mobile device policies (BYOD company-owned), Chrome browser enrollment extension management, and troubleshooting synchronization issues across Workspace services.
Topic 3	Managing User Accounts, Domains, and Directory: This section measures the skills of Identity Administrators and Directory Managers, covering user lifecycle processes like automated provisioning de-provisioning, SAML SSO configuration, and GCDS integration. It includes designing OU hierarchies aligned with organizational structures, managing dynamic security groups, domain verification (MX records), and resource booking permissions for rooms equipment.
Topic 4	Managing Core Workspace Services: Targeting Workspace Configuration Specialists and Collaboration Platform Engineers, this domain focuses on configuring Gmail (mail routing, DLP, SPF DKIM), Drive Shared Drives (sharing policies, quotas), Calendar (resource delegation), Meet (security recording settings), Chat moderation, and Gemini licensing. It also covers AppSheet Apps Script deployment for workflow automation.
Topic 5	Troubleshooting Common Issues: Targeting Technical Support Engineers and Systems Administrators, this domain tests diagnostic skills for mail delivery failures (SPF DMARC analysis), Calendar Drive permission conflicts, Meet performance issues, and accidental file deletion recovery. It emphasizes log interpretation, HAR file generation, and leveraging the Workspace Status Dashboard for outage identification.

NO.47 Your organization has hired temporary employees to work on a sensitive internal project. You need to ensure that the sensitive project data in Google Drive is limited to only internal domain sharing. You do not want to be overly restrictive. What should you do?

Restrict the Drive sharing options for the domain to allowlisted domains.

Turn off the Drive sharing setting from the Team dashboard.

Create a Drive DLP rule, and use the sensitive internal Project name as the detector.

Configure the Drive sharing options for the domain to internal only.

NO.48 Today your company signed up for Google Workspace Business Starter with an existing domain name. You want to add team members and manage their access to email and other services. However, you are unable to create new user accounts or change user settings. You need to fix this problem. What should you do?

Run the Transfer tool to bring unmanaged users to your Workspace account.

Check domain ownership in the DNS settings.

Wait 24 hours after signing up for the features to become active.

Upgrade to a Google Workspace Enterprise edition.

NO.49 A user accessing sensitive data is experiencing repeated issues with accessing certain files in Google Drive from their laptop by using the Chrome browser. When you contact Google support, the support representative asks to review an HTTP archive file recording (HAR). You need to share logs with Google support without compromising data privacy. What should you do?

Open the HAR file in a text editor and delete sensitive information. Upload the HAR file to Google Drive and share the file only with the Google support representative

Ask the Google support representative for access to a Google Drive folder used by the Google support team. Upload the HAR file.

Share your screen with the Google support representative so they can view the file without having a copy of the file.

Upload the HAR file to Google Drive and share the file with the Google support representative.

NO.50 A new user at your organization is unable to access Google Meet. You have verified that the user’s account is active and the correct licenses are assigned. You need to resolve the access issue. What should you do?

Check the user’s browser settings to ensure that Meet is not blocked.

Instruct the user to clear their browser’s cache and cookies.

Restart the user’s computer to refresh their network connection.

Verify that Meet is enabled as a service for the user’s account in the Admin console.

NO.51 Per regulatory requirements, your company is required to keep the data of employees located in Germany within Europe and the data of employees located in the US within the US. The employees in Germany are in a separate organizational unit (OU) than employees in the US. You need to ensure that where employee data is stored is in compliance with the location regulations.
What should you do?

Instruct employees to use Drive for desktop to keep documents on their corporate computers.

Create two Groups. Assign employees into the Germany or US Group based on their location. Use Google Drive trust rules to prevent sharing between the Groups.

Navigate to the Data Regions function in the Admin console. Select the Europe region for employees in Germany, and select the US region for US employees.

Navigate to the Data Regions function in the Admin console. Select ‘No preference.’

NO.52 Several employees at your company received messages with links to malicious websites. The messages appear to have been sent by your company’s human resources department. You need to identify which users received the emails and prevent a recurrence of similar incidents in the future. What should you do?

Search the sender’s email address by using Email Log Search. Identify the users that received the messages. Instruct them to mark them as spam in Gmail, delete the messages, and empty the trash.

Search for the sender’s email address by using the security investigation tool. Mark the messages as phishing. Add the sender’s email address to the Blocked senders list in the Spam, Phishing and Malware setting in Gmail to automatically reject future messages.

Collect a list of users who received the messages. Search the recipients’ email addresses in Google Vault. Export and download the malicious emails in PST file format. Add the sender’s email address to a quarantine list setting in Gmail to quarantine any future emails from the sender.

Search for the sender’s email address by using the security investigation tool. Delete the messages. Turn on the safety options for spoofing and authentication protection in Gmail settings.

NO.53 You manage Chrome Enterprise browsers for your large organization. You want to ensure that specific extensions are automatically installed on all managed Chrome Enterprise browsers. What should you do?

Allowlist the specific Chrome browser extensions.

Configure a script to deploy the extensions upon user login.

Publish the extensions in the Chrome Web Store.

Force-install the extensions through Chrome browser policies.

NO.54 Your organization has experienced a recent increase in unauthorized access attempts to your company’s Google Workspace instance. You need to enhance the security of user accounts while following Google-recommended practices. What should you do?

Disable password recovery options to prevent unauthorized individuals from accessing user accounts.

Implement a strong password policy and enable text messages as the 2-Step Verification (2SV) using text messages.

Enforce the use of physical security keys as the 2-Step Verification (2SV) method for all users.

Enforce a strong password policy that requires users to include special characters, numbers, and uppercase letters.

NO.55 Your company distributes an internal newsletter that contains sensitive information to all employees by email. You’ve noticed unauthorized forwarding of this newsletter to external addresses, potentially leading to data leaks. To prevent this, you need to implement a solution that automatically detects and blocks such forwarding while allowing legitimate internal sharing. What should you do?

Add a banner to the newsletter that warns users that external sharing is prohibited.

Create a Gmail content compliance rule that targets the internal newsletter, identifying instances of external forwarding. Configure the rule to reject the message when such forwarding is detected

Develop an Apps Script project by using the Gmail API to scan sent emails for the newsletter content and external recipients. Automatically revoke access for violating users.

Create a content compliance rule to modify the newsletter subject line, adding a warning against external forwarding.

NO.56 Your company’s help desk is receiving technical support tickets from employees who report that messages from known external contacts are being sent to the spam label in Gmail. You need to correct the issue and ensure delivery of legitimate emails without introducing additional risk as soon as possible. What should you do?

Ask employees to select the messages in Gmail that are being delivered to spam and mark them as Not spam.

Contact the external senders, and tell them to authenticate their sent mail by using domain-based message authentication, reporting, and conformance (DMARC).

Turn off more aggressive spam filtering in spam policies that are applied to the users’ organizational unit and add the senders’ mail system IP addresses to the email allowlist.

Create an address list of approved senders so messages from these users bypass Gmail’s spam filters and recipients can decide whether they are spam or not.

NO.57 Your organization needs an approval application for purchases where a user can enter information on the purchase required and then submit it for management approval. You need to suggest a solution to create the application that must be available on both the web and mobile devices. Your organization does not have software developers or the budget to hire a third party. What should you do?

Suggest that the organization use AppScript to create forms linked to a Google Sheet to store the purchase data.

Suggest that the organization continue to approve requests manually until budget is available to use a third-party application provider.

Suggest the organization use AppSheet to create the application.

Suggest that the organization develop an application internally with a database, a backend service for data retrieval, and a frontend service for the application’s user interface.

NO.58 Your organization needs an approval application for purchases where a user can enter information on the purchase required and then submit it for management approval. You need to suggest a solution to create the application that must be available on both the web and mobile devices. Your organization does not have software developers or the budget to hire a third party. What should you do?

Suggest that the organization develop an application internally with a database, a backend service for data retrieval, and a frontend service for the application’s user interface.

Suggest that the organization continue to approve requests manually until budget is available to use a third-party application provider.

Suggest the organization use AppSheet to create the application.

Suggest that the organization use AppScript to create forms linked to a Google Sheet to store the purchase data.

NO.59 The innovation team at your organization has a dedicated room with prototype equipment. You need to make the room bookable, add the equipment, and ensure that there are no booking conflicts. Only the innovation team and the sales directors can access this room. What should you do?

Create a separate Google Calendar resource for the room. Manually manage booking requests from both teams.

Create a Google Group for the innovation team and another Google Group for sales directors. Share the room’s calendar with both groups.

Create a Google Calendar event for the room. Share the event with the innovation team and sales directors.

Edit the Google Calendar settings for the room resource. Adjust the permission settings so only the innovation team and sales director group can view and book time on this calendar.

NO.60 Your organization’s employees frequently collaborate with external clients and vendors by using Google Meet. There are active instances of unsupervised meetings within your organization that do not have a host, and unsupervised meetings that continue after an event has completed. You want to end all meetings that are being used inappropriately as quickly as possible. What should you do?

End all unsupervised meetings by using the Google Meet APIs.

Enable Host Management for Google Meet, and train internal host employees how to end meetings for everyone.

Turn off Google Meet in the Admin console for your organization. Turn Google Meet back on after two minutes.

Identify and end all unsupervised meetings by using the security investigation tool.

NO.61 The human resources department notified you of a legal investigation that was started for an employee in the finance department. You need to ensure that this employee’s Google Drive data is preserved for at least one year and does not get deleted by the user or by other means. The Google Vault default retention rules for Drive are set for five years. What should you do?

Change the Vault default retention rule to one year instead of five.

Place the employee into a separate organizational unit (OU). Create a custom one-year retention rule for this OU.

Create a hold in Vault for the employee’s Drive.

Confirm that the Vault default retention rule is set for five years.

When there’s a legal investigation, the priority is to ensure that relevant data is preserved and not deleted, regardless of retention policies or user actions. A “hold” (also known as a litigation hold or legal hold) in Google Vault is specifically designed for this purpose. It overrides all retention rules (both default and custom) and prevents any data covered by the hold from being purged, even if a user attempts to delete it.
Here’s why the other options are not the correct or best solution:
A . Change the Vault default retention rule to one year instead of five. Changing the default retention rule would affect all Drive data in your organization, not just this specific employee’s. It’s a broad change and not suitable for a targeted legal hold. Moreover, it wouldn’t guarantee preservation against user deletions.
B . Place the employee into a separate organizational unit (OU). Create a custom one-year retention rule for this OU. While creating custom retention rules for OUs is possible, it’s not the primary mechanism for a legal hold. Retention rules define when data can be deleted, but a hold prevents deletion irrespective of the retention period. If the employee deletes the data, a retention rule won’t stop it from moving to trash (and eventually being purged) unless a hold is in place. Furthermore, a one-year retention rule isn’t the goal; the goal is to preserve for “at least one year” (meaning indefinitely until the hold is released). The default five-year rule is already longer than one year, but doesn’t override user deletion.
D . Confirm that the Vault default retention rule is set for five years. The question states that the default retention rule for Drive is already set for five years. While this is good for general data retention, it does not prevent a user from deleting their own files from Drive, nor does it specifically address the need for a legal hold where data must be absolutely preserved. A default retention rule does not override user deletion or ensure data preservation for legal purposes.
Reference from Google Workspace Administrator:
Holds in Google Vault: This is the core concept. Holds prevent data from being purged from Google systems, regardless of retention rules or user actions, until the hold is released. They are specifically used for legal discovery or investigation purposes.
Reference:
Retention rules in Google Vault: While relevant to data management, retention rules define when data can be deleted if no hold applies. They do not prevent users from deleting data or ensure preservation for legal holds.

NO.62 An employee at your organization may be sharing confidential documents with unauthorized external parties. You must quickly determine if any sensitive information has been leaked. What should you do?

Review the employee’s Drive log events in the security investigation tool.

Audit Drive access by using the Admin SDK Reports API.

Review the employee’s user log events within the security investigation tool.

Create a custom report of the user’s external sharing by using the security dashboard.

To quickly determine if an employee has shared confidential documents externally, you should utilize the security investigation tool in the Google Admin console and specifically review the Drive log events associated with that employee’s account. This tool provides a centralized place to audit user activity related to Google Drive, including sharing actions.
Here’s why option A is the most direct and efficient first step:
A . Review the employee’s Drive log events in the security investigation tool.
The security investigation tool allows administrators to examine various logs related to user activity and potential security incidents. By focusing on the Drive log events for the specific employee in question, you can quickly filter and review actions such as file sharing, permission changes, and external access. This will provide a direct view of whether the employee has indeed shared documents externally and to whom.
Associate Google Workspace Administrator topics guides or documents reference: The official Google Workspace Admin Help documentation on the “Security investigation tool” (or similar titles) explains its capabilities. Specifically, the section on “Investigating Drive log events” details how administrators can use filters to view file sharing activities, including external sharing, by specific users and timeframes. This tool is designed for precisely such scenarios where you need to quickly audit user actions related to data access and sharing.
B . Audit Drive access by using the Admin SDK Reports API.
While the Admin SDK Reports API can provide detailed information about Drive activity, using it requires programming skills and setting up custom scripts or applications. This is not the quickest way to investigate a potential immediate security concern. The security investigation tool offers a user-friendly interface for administrators to perform such investigations without needing to code.
Associate Google Workspace Administrator topics guides or documents reference: The Google Workspace Admin SDK documentation describes the Reports API and its capabilities. While powerful for custom reporting and automation, it’s not the fastest method for a quick, ad-hoc security investigation compared to the built-in security investigation tool.
C . Review the employee’s user log events within the security investigation tool.
The user log events in the security investigation tool cover a broader range of activities beyond just Google Drive, such as login attempts, password changes, and device management actions. While this might provide some context, it is less focused on file sharing activities compared to the Drive log events. To quickly determine if confidential documents were shared, filtering directly for Drive-related actions is more efficient.
Associate Google Workspace Administrator topics guides or documents reference: The documentation on the security investigation tool outlines the different log sources available, including user logs and Drive logs. For investigating file sharing, the Drive logs provide more specific and relevant information.
D . Create a custom report of the user’s external sharing by using the security dashboard.
The security dashboard provides an overview of your organization’s security posture and includes pre-built reports and insights. While you can create custom reports, this process might take longer than directly investigating the Drive log events for the specific employee in the security investigation tool. The investigation tool is designed for targeted and immediate analysis of potential security incidents related to user actions.
Associate Google Workspace Administrator topics guides or documents reference: The Google Workspace Admin Help documentation on the “Security dashboard” explains its features, which focus on overall security trends and insights. While it can be useful for identifying patterns, the security investigation tool is more suited for investigating specific user actions and potential data leaks on demand.
Therefore, the most efficient and direct way to quickly determine if the employee has shared confidential documents externally is to review the employee’s Drive log events in the security investigation tool.

NO.63 Your company’s sales team writes many business proposals in Google Docs. They want to streamline the proposal process by using templates. You need to create a document template with pre-populated sections that the sales team can access. What should you do?

Create the templates in Google Drive. Grant edit access to the sales team.

Create the templates in Google Drive. Make a copy for each sales representative. Transfer ownership of each template to the sales representatives.

Enable organization branding in the Admin console. Create the templates in Google Drive. Add the templates to default themes and templates for the entire organization.

Create the templates in Google Drive and download the files as PDFs. Upload PDF files to a drive shared with your sales team.

To create document templates with pre-populated sections that the sales team can easily access and use to streamline their proposal process, the most efficient and centrally managed approach is to utilize the Google Workspace template gallery. This involves enabling organization branding (though not strictly required for basic templates, it’s often associated with organizational templates) and then adding the created templates to the default themes and templates for the entire organization or specific groups.
Here’s a breakdown of why option C is correct and why the others are not the ideal solutions:
C . Enable organization branding in the Admin console. Create the templates in Google Drive. Add the templates to default themes and templates for the entire organization.
This option leverages the built-in template gallery feature of Google Workspace. By creating the templates in Google Docs (which are stored in Google Drive) and then adding them to the organization’s default themes and templates through the Google Admin console, you make these templates easily discoverable by all users (or a specific organizational unit) when they go to create a new document from the template gallery. Enabling organization branding can help customize the look and feel, but the crucial part is adding the templates to the gallery.
Associate Google Workspace Administrator topics guides or documents reference: The official Google Workspace Admin Help documentation provides detailed instructions on “Create and manage document templates for your organization.” This documentation explains how to prepare a document as a template in Google Drive and then submit it through the Admin console to the template gallery, making it available to users within the organization. Topics covered include:Submitting templates to your organization’s gallery: This process involves going to Apps > Google Workspace > Drive and Docs > Templates in the Admin console.
Setting up a custom template gallery: The documentation guides administrators on how to manage the templates that appear for their users.
Organizational units: Templates can often be made available to specific organizational units, allowing for tailored templates for different teams like the sales team.
A . Create the templates in Google Drive. Grant edit access to the sales team.
Granting edit access to the sales team on the master templates is problematic. It could lead to accidental or intentional modifications of the original templates, causing inconsistencies and requiring ongoing management to ensure the templates remain in their intended state. Users should ideally create copies of the template to work on, leaving the original template untouched.
Associate Google Workspace Administrator topics guides or documents reference: Best practices for file sharing and collaboration in Google Drive emphasize providing appropriate levels of access. For templates, the goal is usually for users to use the template to create new documents, not to edit the original.
B . Create the templates in Google Drive. Make a copy for each sales representative. Transfer ownership of each template to the sales representatives.
This approach is inefficient and difficult to manage. Creating and transferring ownership of individual copies of the template to each sales representative would be time-consuming for the administrator. Furthermore, if the template needs to be updated, each individual copy would need to be modified, leading to version control issues and inconsistencies across the sales team.
Associate Google Workspace Administrator topics guides or documents reference: Google Drive’s sharing and ownership features are designed for collaborative work on documents, not for distributing and managing templates in this manner. Centralized management through the template gallery is the recommended method.
D . Create the templates in Google Drive and download the files as PDFs. Upload PDF files to a drive shared with your sales team.
Saving the templates as PDFs defeats the purpose of having editable templates. The sales team would not be able to easily modify the pre-populated sections or add their specific proposal details to a PDF. Templates are meant to be starting points for new, editable documents.
Associate Google Workspace Administrator topics guides or documents reference: Google Docs is designed for creating and editing documents. Templates are a feature within this editable format, allowing users to start with a pre-structured document that they can then customize. PDFs are for final, non-editable versions.
Therefore, the correct approach is to leverage the Google Workspace template gallery to provide a streamlined and centrally managed way for the sales team to access and use the proposal templates. This is achieved by creating the templates in Google Drive and then adding them to the organizational templates through the Admin console. While enabling organization branding is mentioned in option C, the core functionality relies on the template gallery feature.

NO.64 Your organization allows employees to use their personal mobile devices to check their work emails. You need to remove the employee’s work email data from their phone when they leave the organization. What should you do?

Set up basic mobile management on the devices.

Set up data protection rules to prevent data sharing externally.

Set up advanced mobile management on the devices.

Set up 2SV authentication on the devices.

NO.65 You are applying device and user policies for employees in your organization who are in different departments. You need each department to have a different set of policies. You want to follow Google-recommended practices. What should you do?

Create separate top-level organizational units for each department.

Create an Access group for each department. Configure the applicable policies.

Add all managed users and devices in the top-level organizational unit.

Create a child organizational unit for each department.

Google recommends using the organizational unit (OU) structure for applying different settings and policies to different groups of users and devices within your Google Workspace domain. To apply a unique set of policies to each department, you should create a child organizational unit for each department under your main domain structure.
Here’s why option D aligns with Google’s best practices and why the others are less suitable:
D . Create a child organizational unit for each department.
Organizational units provide a hierarchical structure for managing users and devices. By creating a child OU for each department, you can then apply specific device and user policies to that OU. Users and devices within a child OU inherit policies from parent OUs but can also have OU-specific policies that override or supplement the inherited ones. This allows for granular control and ensures that each department can have the policies tailored to its needs. This is the recommended method by Google for managing policies based on departments or other logical groupings within an organization.
Associate Google Workspace Administrator topics guides or documents reference: The official Google Workspace Admin Help documentation on “How the organizational structure works” and “Apply settings for specific groups of users or devices” (or similar titles) clearly explains the purpose and benefits of using OUs for policy management. It emphasizes the hierarchical nature and how policies are applied and inherited through the OU structure. Creating child OUs for departments is a direct application of this recommended practice.
A . Create separate top-level organizational units for each department.
Creating separate top-level OUs for each department is generally not recommended for managing policies within the same organization. Top-level OUs are meant to represent distinct functional or administrative units that might have their own domain settings and administrators. Managing all departments under a single domain but in separate top-level OUs can complicate overall administration, sharing, and user management across the organization. Child OUs within a single domain provide the necessary separation for policy application while maintaining a unified organizational structure.
Associate Google Workspace Administrator topics guides or documents reference: Google’s documentation on organizational structure usually advises on creating a logical hierarchy of child OUs under a single top-level OU representing the organization. Separating departments into top-level OUs is not a standard or recommended practice for policy management within a single domain.
B . Create an Access group for each department. Configure the applicable policies.
Access groups are primarily used for controlling access to specific resources or services. While you can manage group membership based on departments, policies for users and devices are typically applied at the organizational unit level, not directly to access groups. While some settings might be influenced by group membership, OUs are the primary mechanism for policy enforcement.
Associate Google Workspace Administrator topics guides or documents reference: The Google Workspace Admin Help distinguishes between organizational units and groups (including access groups). Policies are consistently described as being applied to OUs. Groups are for managing access and collaboration.
C . Add all managed users and devices in the top-level organizational unit.
Applying all policies at the top-level OU would mean that all users and devices inherit the same set of policies. This contradicts the requirement of having different policies for each department. To achieve department-specific policies, you need to organize users and devices into separate OUs.
Associate Google Workspace Administrator topics guides or documents reference: Google’s documentation emphasizes the flexibility of the OU structure to apply different policies to different subsets of users and devices. Placing everyone in the top-level OU negates this flexibility.
Therefore, the Google-recommended practice for applying different device and user policies to employees in different departments is to create a child organizational unit for each department. This allows for targeted policy application and management within the overall organizational structure.

NO.66 Your organization’s security team has published a list of vetted third-party apps and extensions that can be used by employees. All other apps are prohibited unless a business case is presented and approved. The Chrome Web Store policy applied at the top-level organization allows all apps and extensions with an admin blocklist. You need to disable any unapproved apps that have already been installed and prevent employees from installing unapproved apps. What should you do?

Change the Chrome Web Store allow/block mode setting to allow all apps, admin manages blocklist, In the App access control card, block any existing web app that is not on the security team’s vetted list.

Change the Chrome Web Store allow/block mode setting to block all apps, admin manages allowlist. Add the apps on the security team’s vetted list to the allowlist.

Disable Extensions and Chrome packaged apps as Allowed types of apps and extensions for the top-level organizational unit. Selectively enable the appropriate extension types for each suborganization

Disable the Chrome Web Store service for the top-level organizational unit. Enable the Chrome Web Store service for organizations that require Chrome apps and extensions.

NO.67 You are migrating your organization’s email to Google Workspace. Your organization uses the terramearth.com email domain. You need to configure Google Workspace to receive emails sent to terramearth.com. What should you do?

Add terramearth.com as a primary, secondary, or alias domain in Google Workspace. Update the Mail Exchange (MX) records with your domain registrar to direct mail flow to Google’s mail servers.

Establish a Transport Layer Security (TLS) connection between your company’s existing mail servers and Google’s mail servers

Configure an email address in Google Workspace to capture emails sent to unverified domains, including terramearth.com.

Create a domain alias for terramearth.com in Google Workspace. Configure email forwarding to redirect emails to the new Google Workspace accounts.

NO.68 You work at a large organization that prohibits employees from using Google Sites. However, a task force comprised of three people from five different departments has recently been formed to work on a project assigned by the Office of the CIO. You need to allow the users in this task force to temporarily use Google Sites. You want to use the least disruptive and most efficient approach. What should you do?

Turn Google Sites access on for each of the 15 users in the task force.

Create a configuration group for the task force’s 15 users. Grant Google Sites access to the group.

Place the 15 task force users into a new organizational unit (OU). Turn on Google Sites access for the OU.

Create an access group for the task force’s 15 users. Grant Google Sites access to the group.