The Google Workspace connector reads users, groups, admin roles, login events, admin events and token events. With response actions, it can propose signing a user out, changing whether a user is suspended, removing or restoring a group member, and revoking OAuth tokens or app passwords. Every change still needs an approved plan.
Before you start
- You need a Google Workspace super administrator to approve access in the Google Admin console. Vigilbase never sees a password.
- In Vigilbase OS you need the
integration.manageandcredential.managepermissions.
Connect with guided setup
Open Integrations, choose Add connection and select Google Workspace. Choose Continue.
Your domain. Enter your Primary domain, as shown in the Google Admin console, for example
example.com.Prove you own it. Add the DNS record the page shows to your domain. DNS changes can take a few minutes, sometimes longer.
Allow Vigilbase in Google Admin. Open the Google Admin console page for domain-wide delegation, choose Add new, paste the client ID and the scopes shown on the page, then choose Authorize.
Sign in as an administrator. Choose Sign in as a Google Workspace admin. Vigilbase reads as this administrator.
Finish. Confirm the Administrator email and finish setup. Google can take up to a minute to confirm delegation.
If you prefer, choose Use your own service account instead.
Response actions
Signing a user out, changing suspension and revoking OAuth tokens or app passwords are irreversible. Signing out, changing suspension and changing group membership are marked critical, so the person who proposes them can never approve them.