When experiencing a potential service disruption with a Google product like Chrome browser that is impacting your organization, the first and most efficient step to check for known outages and their resolution timelines is to review the Google Workspace Status Dashboard. This dashboard provides real-time information about the status of various Google Workspace services, including Chrome Enterprise.

Conduct regular security awareness training to educate users: Educating users about phishing threats and safe online practices can help them recognize and avoid phishing attempts, reducing the chances of them falling for such scams.
Create a Drive trust rule that blocks all external domains except for a pre-approved list of trusted partners: By setting up a Drive trust rule to limit access to files from external domains, you can block links to malicious files hosted on untrusted external Google Drives while still allowing access to legitimate external files from trusted sources.

When a third-party application from the Google Workspace Marketplace is installed, it requests specific permissions (OAuth scopes) to access Google Workspace data and services. If the marketing team is unable to access customer contact information or send emails, the most likely cause is that the installed email marketing platform was not granted the necessary OAuth scopes for Contacts and Gmail during the installation or approval process.
Here's why other options are less likely to be the first step:
A . Verify that the email marketing platform's subscription is active and up-to-date. While important for continued use, a "free" platform from the Marketplace generally doesn't have a subscription that would prevent initial access to basic functions like contacts and sending emails unless it's a trial that expired, which isn't indicated as the primary problem. This would be a later troubleshooting step if scope issues are ruled out.
C . Confirm that the "Manage Third-Party App Access" setting in the Admin console is enabled. This setting controls whether users can install any third-party apps from the Marketplace. If it were disabled, the app likely wouldn't have been installed in the first place. If it was enabled and then disabled, the app would stop working, but the specific problem points to data access, not app disablement.
D . Use the security investigation tool to review Gmail logs. The security investigation tool is excellent for reviewing security events, but it's more for post-incident analysis or suspicious activity. In this scenario, the problem is a lack of functionality for a newly installed app, not a security breach or misconfiguration that would necessarily show up in Gmail logs immediately as an access issue for the app itself. The OAuth scopes are the more direct and initial point of failure.
Reference from Google Workspace Administrator:
Manage third-party app access to data: Google Workspace administrators can control which third-party apps can access their organization's data. This includes reviewing and managing OAuth API access for configured apps.
Reference:
Understanding OAuth scopes: When an application requests access to Google data, it does so by requesting specific "scopes." These scopes define the particular resources and operations that the application is allowed to perform. For an email marketing platform, scopes for https://www.googleapis.com/auth/contacts (or a more specific contact scope) and https://www.googleapis.com/auth/gmail.send (or a broader Gmail scope) would be crucial.
Controlling which third-party & internal apps can access Google Workspace data: This section in the Admin console specifically allows administrators to review "Configured apps" and check their "OAuth API access." This is where you would see the scopes granted to the email marketing platform.

AppSheet is a no-code platform that allows users to create custom applications without the need for software development skills. It is capable of building applications that can be used both on the web and mobile devices. AppSheet would allow the organization to create the approval application efficiently, meeting the requirements of the purchase process, and would be a cost- effective solution that does not require hiring developers or using a third-party application provider.

When an internal user reports not receiving Google Calendar event invites, the most likely immediate cause to investigate on the recipient's end is their notification settings within Google Calendar. Users can customize their notification preferences, and it's possible they have turned off email notifications for new events.
Here's why option D is the most relevant first step and why the other options are less likely to be the primary cause of this specific issue:
D . Check whether the event recipient has turned off their email notifications for new events in their Calendar settings.
Google Calendar allows users to configure various notification settings, including whether they receive email notifications for new events, changes to events, reminders, etc. If the recipient has disabled email notifications for new events, they would not receive the invites in their inbox, even though the event might be correctly added to their Calendar.
Associate Google Workspace Administrator topics guides or documents reference: The official Google Calendar Help documentation for users, such as "Change notification settings," explains how users can customize their event notifications. This includes options to turn off email notifications for new events. While administrators don't directly manage individual user's notification settings, understanding these user-level controls is crucial for troubleshooting. An administrator might guide the user to check these settings.
A . Check whether the business hours are set up in the event recipient's Calendar settings.
Business hours in Google Calendar primarily affect meeting scheduling suggestions and how a user's availability is displayed to others. They do not directly prevent a user from receiving event invitations. Whether or not a recipient has configured their business hours will not stop the email notification for a new event from being sent (unless perhaps in very specific and unusual edge cases related to resource scheduling, which isn't indicated here).
Associate Google Workspace Administrator topics guides or documents reference: The Google Calendar Help documentation on "Set your working hours and location" explains the purpose of business hours, which is related to availability and scheduling, not the receipt of invitations.
B . Check if Calendar service is turned off for the event creator.
If the Calendar service is turned off for the event creator, they would not be able to create or send any Calendar events in the first place. Since the user created and sent the invite (as mentioned by the recipient not receiving it), the Calendar service must be active for the creator.
Associate Google Workspace Administrator topics guides or documents reference: The Google Workspace Admin Help documentation on "Turn Google Calendar on or off for users" explains how administrators can control access to the Calendar service. If the service is off for a user, they would not have Calendar functionality.
C . Check whether the Calendar event has more than 50 guests.
While there might be limitations on the number of guests that can be added to a single Calendar event, exceeding this limit typically results in an error message for the event creator during the invitation process, not a failure of the recipient to receive the invite. Even if there were such a limit affecting receipt (which is not a common documented issue for internal users within reasonable limits), it wouldn't be the first thing to check.
Associate Google Workspace Administrator topics guides or documents reference: Google Calendar Help documentation might mention limits on the number of guests, but these limits usually pertain to the ability to add guests, send updates, or view responses, not a complete failure of delivery to some recipients within the organization.
Therefore, the most logical first step in troubleshooting why an internal recipient isn't receiving Calendar event invites is to have the recipient check their own Calendar notification settings to ensure that email notifications for new events are enabled.