Customization Options - Google Button

This article describes how to create and customize the Google button. Complete the process with Installation Instructions - Google Button.

To create a new button:

1. Navigate to System > Button Plugin Config.

2. On the Button Configuration Manager page, click New.

3. Enter a Configuration Name, a user-friendly name you will use for this button configuration. This name is not visible to users.

4. Select a Code Version to specify the type of button you want to create – Google – and the software version used for this configuration. Other configurations are described in other articles. 

5. Click Save. 

6. Specify the configuration based on the descriptions below, then click Save again. 

   General

   • • Configuration Name – The name you specified above is copied here. You can change it at this point if you choose.

   Code Version

   • • Code Version – Version of the software code you chose for this configuration in Step 4 above.
     • Button Code Type – Displays the type of source code for the selected Code Version.
     • Code Description – Displays the description of the selected Code Version.

   Button Image

   • • Button Image – Select and upload a graphics file to display on the button.
       Recommendation: Select a GIF or PNG file. If needed, the system will automatically resize the image to approximately 80 x 80 pixels.
     • Button Image File Type – Displays the type of file you uploaded for the Button Image (GIF or PNG).
     • Button Image File Size – Displays the size of the image file you selected and uploaded.

   Instructions

   This section includes the ZIP file needed to install the Google button. You will come back to this section later. 

   General Settings

   • • Include Original Subject – Select to include the subject of the reported email in the subject line for the message wrapper email.
     • Are You Sure - Enable – Select to prompt users to verify that they want to report the selected email.
       If you enable Are You Sure, specify the following options or accept the defaults: 
       
       • Are You Sure - Title – Bold headline displayed when user reports an email.
       • Are You Sure - Prompt Text – Text displayed under the headline when a user reports an email. 
     • Disable Internal Delete – Select to save internal emails, rather than deleting them, when reported by the user via the main button. 

   Phishing

   • • Phishing Button Label – Enter a text label for the phishing button.
     • Phishing Report Email Subject – Enter a subject line for emails reported with the phishing button. Use {0} to use the original subject.
     • Phishing Body Text – Enter body text for the reported email when it is not classified as a mock phishing test or an internal message.

     To see reported email information within Security Awareness Training, include your Security Awareness Training email address (phishline_<Instance_Name>@phishline-incident-response.com) in the Send To fields in one or more of the sections below.
     Message detail is available in Results > Inbox Analysis and Results > Incident Response. For more information, refer to Inbox Analysis and Incident Response.
     Users who report campaign emails receive credit, shown in Results > Outbound Analysis. For more information, refer to Outbound Analysis.

     Internal Message

   • • Internal Send To – Enter one or more email addresses to notify of reported emails from the internal domains. Separate multiple email addresses with semicolons or commas. For visibility within Security Awareness Training, include phishline_<Instance_Name>@phishline-incident-response.com. See note above. 
     • Internal Reporting Success Pop Up Message – Optional. Enter text to appear to users when they report a phishing message from an internal domain.
     • Reported Internal Body Text – Enter the body text for the reported phishing email when it is recognized as Internal. Use {0} to insert the matching internal domain.
     • Internal Domains – Enter a list of domains that the plugin will use to identify reported emails that came from your internal domains. Enter one domain per line in the format example.com.

   Mock Message

   • • Mock Send To – Enter one or more email addresses to notify of reported emails recognized as Mock Phishing tests. Separate multiple email addresses with semicolons or commas. For visibility within Security Awareness Training, include phishline_<Instance_Name>@phishline-incident-response.com. See note above. 
     • Mock Success Message – Optional. Enter text to appear to users when they report a mock phishing message. 
       
     • Reported Mock Body Text – Enter the body text for the reported email when it is recognized as a mock phishing test. Use {0} to insert header information.
     • Mock Phishing Headers – Enter a list of X-Headers, one per line, to identify mock phishing emails. Configure custom X-Headers in System > Global Settings. X-Headers can be any string of alphanumeric characters. Choose a string that does not identify the function of the X-Header and is unique enough not to be duplicated by another process. An example of an X-Header for this use is X-AEDE112EDA.

   Not Internal or Mock

   • • Phishing Report Send To – Enter one or more email addresses notified when a user clicks the phishing button, but the suspect emails are neither Mock nor Internal. Separate multiple email addresses with semicolons or commas. For visibility within Security Awareness Training, include phishline_<Instance_Name>@phishline-incident-response.com. See note above. 
     • Phishing Success Message – Enter an optional message that will be shown to users for every reported phishing message that is not Mock or Internal.

   2-Step Button

   This feature is not available with the Google button.

   Spam

   This feature is not available with the Google button.

   
   
   

7. Scroll back up to Instructions section. Click on the ZIP file to download it. The name of the ZIP file looks something like ReportPhishGoogleChromeExtension...zip.
8. Expand the content of the ZIP file. It contains:
   
   • README.html – A file directing you to these instructions. 
   • google_button_config.json – The Policy file that you will upload to Google through your Google Admin account. 
   • imagetest.html – A small HTML file used to verify that the uploaded image was encoded correctly in the configuration.
   • <2.2.8.1.zip> – The ZIP file you will send to the Chrome Web Store. As of this writing, the file name is 2.2.8.1.zip.
9. Log into the Chrome Web Store, https://chrome.google.com/webstore/, using your Google admin account and upload the ZIP file from the previous step <2.2.8.1.zip.>. 
10. Within the Chrome Web Store, make the following recommended/required settings:

    • Description – Longer text users will see. For example: The report phishing button. Please report any suspected phishing attempts. 

    • Icon – Graphic to be used for the button. There are icon choices in the 2.2.8.1.zip file. Recommended: phish128.png.

    • Category – Select Productivity.

    • Language – Select English.

    • Visibility Options – Select Private > Everyone at (yourdomain.com)

    • Screenshot – Add a 640 x 400 screenshot of your choice.

11. Click Save as draft and return to Dashboard.

12. Click Publish.
    Wait for the status to change from 'Pending Review'. You can refresh the page to check status. This stage depends on the Google review process and can take anywhere from 2 hours to several days.

13. Click More Info to see the 32-character randomly-generated ID that Google uses to identify the extension. Copy this ID. You will need it in the Creating OAuth User Credentials section of Installation Instructions - Google Button.

While you are waiting for the review process to complete, continue the process with Installation Instructions - Google Button.