• Home
  • Features
  • Pricing
  • Documentation
  • Contact Us
  • Support
Sign In
Client Portal

Getting Started

  • Post-Install Setup Guide
  • Email Settings
  • Email Templates
  • POP3/IMAP Settings Guide
  • Email Piping
  • Upgrade and Migration

Guides

  • Alerts Guide
  • Translation Guide
  • OAuth2 Guide

Panels

  • Admin Panel
  • Agent Panel
  • User Portal

Features

  • Multifactor Authentication
  • Visibility Permissions
  • Previously Released

Plugins

  • Attachments in S3
  • Grievance App Audit
  • Two Factor Authentication
  • Password Management Policies
  • Attachments on the Filesystem

Developer Documentation

  • API
  • Changelog
  • Database ERDs
  • Home
  • Docs
  • Google Authentication (SSO) Guide

Google Authentication (SSO) Guide

Google OAuth allows Agents and Users to sign into the  Grievance App with their Google account.

Configuration #

Choose ‘Google’ in the ‘Add New Instance’ menu

oauth43_google_instGive the instance a name that lets you know which provider is selected and select ‘Enabled’ for the status.

oauth42_enable_instGo to the ‘Config’ tab to set up this provider. Some of the default information will be autofilled.

Note: The ‘Authentication Label’ field is the text that will be displayed to the User or Agent when they sign into the  Grievance App.

oauth45_google_cfgChoose an Authentication Target to specify who should be able to use this provider.

oauth46_audienceNow you need to set up a project using the Google Developer Console.

Once you are in the console, click ‘Select a Project’ to get started.

Note: If you already have a project set up for your Google account, its name will be displayed here.

oauth47_google_projClick ‘New Project’ in the modal:

oauth49_google_projGive the project a name and click ‘Create’

oauth50_create_projClick ‘OAuth consent screen’

oauth51_consentHere you will select a User Type of Internal or External. If you do not have a Google Workspace account you will be limited to External only. Please note, if you select Internal only users within your Organization will be able to authenticate. If you select External anyone with a Google account can authenticate, however, the Project will initially be in “Testing Mode”. Once you select your User Type click Create.

oauth52_audienceName your app and fill in your support email. Optionally, you can upload a logo.

oauth53_appinfoYou can add your website URL if you will be using a domain that you own.

oauth54_app_domainAdd your contact information:

oauth55_contactScopes can be set to extend the permissions between your application and Gmail accounts. You do not need to add any scopes to use OAuth for a typical Gmail account.

oauth56_scopes1oauth57_scopes2Add addresses for emails you want to test with this application. Applications that are in ‘Testing’ mode can add up to 100 test users.

Note: The addresses must be valid Gmail accounts.

oauth99_test_usersoauth911_save_usersClick ‘Save and Continue’ to see an App Summary.

oauth61_summary1Once saved, navigate to the ‘Credentials’ section

oauth63_credsClick ‘Create Credentials’ and select ‘OAuth client ID’

oauth64_credsChoose ‘Web Application’ and name the App

oauth66_create_credsThe Authorized redirect URI can be found in the plugin instance created in osTicket.

oauth67_blank_redir_urioauth68_ost_redir_uriClick ‘Add URI’ from the Google console

oauth69_google_redir_uriThe Authorized JavaScript is just your hostname without anything extra at the end.

oauth70_js_originAdd the JavaScript origin and click ‘Create’.

oauth71_js_originNow you will see your Client ID and Client Secret

oauth72_client_infoCopy the Client ID and Client Secret and paste them into the appropriate fields in the  Grievance App Instance:

oauth73_ost_client_infoThe rest of the information should be autofilled

oauth74_autofilledClick ‘Add Instance’

oauth75_google_add_instNow that the setup is complete, you should be able to use your Google account to log into the  Grievance App.

Agent Login #

To test the functionality for Agents, go to:

Admin Panel | Agents

oauth76_gmail_agentMake sure you have an Agent in your  Grievance App with the same email address as the Google account you want to log in with.

You should also ensure that you see the provider that was just set up in the list. It is important, however, to make sure you choose ‘Use any available backend’ so that you can still log into your  Grievance App in the event that OAuth has an error.

Log out of the  Grievance App and go to the login screen.

oauth77_login_screenClick the ‘Sign in with Google’ button to test the OAuth set up.

Note: The sign in button text can be configured by changing the Authentication Label in the  Grievance App instance setup.

oauth77_login_screenThis should navigate to choose the Google account you want to sign in with

oauth78_choose_gmailNow you should be logged into your  Grievance App.

oauth79_google_logged_in

User Login #

For users, logging in with a Gmail account should create a new User if one does not exist, otherwise, it will log in as an existing User.

oauth80_user_portaloauth81_user_loginThis should also navigate to choose the Google account you want to sign in with.

oauth78_choose_gmailChoose your account and you should be logged in as a User.

Still stuck? How can we help?

How can we help?

Updated on May 21, 2025
Table of Contents
  • Configuration
  • Agent Login
  • User Login

Want to receive news and updates?


    Fuel your business growth and witness immediate results today.

    Features
    • Grievance Routing
    • Mobile Submission
    • Anonymous Entry
    • Form Customization
    Resources
    • Support center
    • Documentation
    • Community Forums
    • Developer API
    Company
    • About us
    • Latest news
    • Success Stories
    • Careers
    Social
    • LinkedIn
    • Facebook
    • Twitter
    • Youtube

    © Grievance.app 2025. All Rights Reserved.

    • Terms & Conditions
    • Privacy Policy