Skip to main content
The common use is a Google Workspace ticket: offboard a leaver, give a manager access to a mailbox, reset a password, or check an account that looks compromised. The agent does it through your WOSP in the tenant mapped to the ticket’s company, and notes each step on the ticket.
Automatically enabled when you configure WOSP permissions in your agent workflow.

​
What It Does

  • Find users and suspend, restore, archive, delete or sign them out, set a new password, add aliases, and change their org unit and profile
  • Create groups, add and remove members, and change group settings
  • Set out of office, forwarding, IMAP and POP, mailbox delegates and send-as addresses, and remove Gmail filters
  • Read licences and seats, and assign or remove a licence
  • Read devices and Chrome browsers, and disable, approve or block a device
  • Read storage and shared drives, add and remove members, and move a user’s Drive files to another user
  • Read alerts, WOSP’s audit findings, admin roles, third-party apps and audit reports, and revoke an app’s access
  • Read each tenant’s last collection, run collection again, and start onboarding a new customer

​
Permission Groups

Neo always asks a technician before it renames, updates or deletes a tenant or hides it from the API, wipes, powerwashes or deprovisions a device, replaces a user’s Gmail settings, edits a building or calendar resource, or changes WOSP’s sign-in or Google OAuth setup, whatever the group’s approval setting. It never reads or sends a Google service-account key, never creates or revokes WOSP API keys, and never changes WOSP’s own settings, which a WOSP admin changes in WOSP. On a ticket, the agent works only on the WOSP tenant mapped to the ticket’s company.

​
Setup

See Connecting WOSP to Neo.