Installation/Deployment of the Phish Tool Button

First, go to script.google.com and click on the New Script button. It is recommended that you use the Legacy editor version of script.google.com for the following instructions.

 Figure 1
Figure 1.2
Figure 1. Creating a new script

The new script file that is opened is saved with a project name.

Figure 2. Creation of a new project

In the Code.gs, paste the Script code provided by Platform to you and save it.

Figure 3. Pasting script codes provided by Platform to Code.gs
Figure 4. Saving the Script code provided by Platform

Then follow View> Show manifest file path and create the appscript.json file.

Figure 5. Creating appscript.json file

Then copy the Manifest code provided by Platform to the screenshot below.

Figure 6. Copying the manifest codes to appscript.json

Go to console.cloud.google.com and create a new project.

Figure 7. Creating a new project

Name your project and select its location. Then click on the Create button to start your project.

Figure 8. Naming and creating the new project

Following the creation of the project, go to the APIs & Services --> OAuth consent page. 

image (17)
Figure 9. Go to OAuth content screen

On the OAuth content screen, select the logo, fill in the required fields, and then click the Save button. At this point in the process, you are choosing whether or not the Gmail add-on will be visible publicly or only to your organization (Internally) within Google Marketplace.
 

 
Figure 10. Filling and saving the required information on the OAuth content screen

Then go to console.cloud.google.com and go to the project settings by clicking the Project settings button like in the screenshot below.

Figure 11. Going to the Project setting page

Copy the Project number value on Project Settings page.

Figure 12. Copying the project number

Follow Resources> Cloud Platform project path on Script.google.com.

Figure 13. Cloud Platform project page

Then, on the Cloud Platform project page, paste Project number in the field and then click Set Project button.

Figure 14. Setting the project

Then confirm the project change.

Figure 15. Confirming the project change

After the project change is confirmed, the change becomes successful.

Figure 16. Successful completion of project change

Then go to your console.cloud.google.com tab and go to APIs & Services > Library.

 Figure 17. Go to Library
Search for Google Workspace Marketplace SDK and enable it. Click on (1) App Config. > (2) Click on Google Workspace Add-On > (3) Select Deploy using Apps Script deployment id. 

Figure 18. Configure Google Workspace Marketplace SDK. 

Go back to your scipt.google.com tab. Then follow Publish> Deploy from manifest.

Figure 19. Publishing the add-in code

Fill the fields highlighted in the following screenshot in order and click on the Create button.

 
Figure 20. Filling the deployment name and version information

Clicking on the Get ID button and copy Deployment ID value from Deployment just created.

Figure 21. Displaying the Deployment ID with Get ID button

In the Deployment ID windowcopy the Deployment ID value. (Note: Since this copied value will be used for the later step -shown in Figure 28- , we recommend you to save it in a notebook)

Figure 22. Copying the Deployment ID

Go back to the console.cloud.google.com tab and enter the Deployment ID in the Google Workspace Marketplace SDK app configuration screen as seen in Figure 18. Fill out the required fields and click Save
___________
Figure 23 Updated (1)
Figure 23. Fill in the required fields. 

Go to the Store Listing tab. Upload the logos and screenshots provided by Platform and fill in the required fields.

 
Figure 24. Uploading the logos and filling the required fields

Select category, related region, and the App Visibilty. (it is suggested to make it private so that it doesn't have to go thru Google review). Then click the Save button and then click Publish.


 Figure 25. Selection of category and related region and publication of changes

As seen in Figure 17, go to Library and search for Gmail API. Enable the Gmail API.

Figure 26. Gmail API Enabling

You can use the Quick Link appeared in the notification box for a quick access to the Marketplace .

Or go to admin.google.com and click on the Apps button to go to applications.

Figure 27. Going to Applications

Click on the plus button to go to the application market.

Figure 28. Application Market

In the application market, find the add-in click on the Domain Install button to start the distribution/deployment process.

Figure 29. Starting the deployment of the add-in

(Remember: If your organization restricts Google Marketplace App Installs, make sure to whitelist this application. Refer to instructions at the bottom.)

Click Continue to start the extension distribution and follow the setup wizard. You will need to accept the permissions needed for the app. After the permissions are accepted, the deployment is successfully completed.
__________________________________________________________________
Where to Whitelist the application as a Google Admin:

If your organization manages App access, then bullet number (3) in the screenshot will be selected. To allow the new App you created to be downloaded, click on Manage Allow list and add your App to the list.