From 4e24a32c468738288c74a3f9696cfe1346ef8317 Mon Sep 17 00:00:00 2001
From: Charlie Chance <100798688+CharlotteChance@users.noreply.github.com>
Date: Tue, 30 Aug 2022 07:23:17 -0600
Subject: [PATCH] Handbook: API-access requests (#7442)

https://github.com/fleetdm/confidential/issues/1541
---
 handbook/security/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/handbook/security/README.md b/handbook/security/README.md
index 00f813e011..6ae565a46f 100644
--- a/handbook/security/README.md
+++ b/handbook/security/README.md
@@ -637,7 +637,7 @@ Google Workspace makes it easy for users to add tools to their workflows while h
 
 This level of security allows users to authenticate to web applications with their Google accounts. This exposes little information beyond what they would provide in a form to create an account, and it protects confidential data while keeping everything managed.
 
->To get an application added to Fleet's Google Workspace security configuration, create an issue assigned to the security team in [this repository](https://github.com/fleetdm/confidential/issues).
+>To get an application added to Fleet's Google Workspace security configuration, create an issue and assign it to the security team in [this repository](https://github.com/fleetdm/confidential/issues). You'll need to include: the client ID in text (not a screenshot) in your issue. This is processed quickly (about 1-2 days) by the Head of Security. The Head of Security will do the research on permissions the app is requesting and determine approval for the app.
 
 We mark every Google Service as *restricted* and recommend that anyone using Google Workspace mark at least the following as restricted in *Security/API Control/Google Services*:
 * Google Drive