# Google Workspace admin, handled from Slack and Teams

Risotto takes the Google requests it sees most often: password and 2-Step resets, Google Group requests, and the calendar and Drive a leaver left behind. Employees ask in Slack or Microsoft Teams and get it done in the thread. The jobs you script by hand today, you build in Risotto by asking.

[Book a demo](/demo) · [Risotto and Google Workspace](/integrations/google-workspace)

## Turn the jobs you script into tools

Risotto calls the same Google APIs your admin scripts do, so a job you run by hand becomes a tool anyone can use. Priya asks for the one she does whenever an exec's assistant needs to manage the boardroom: share its calendar. The Risotto Assistant finds the endpoint in its Google Calendar API template and writes a script tool, Grant room calendar access, that asks for one scope: calendar.acls. She publishes it, approves that scope with Reconnect, and a test run makes Maya Chen a writer on Boardroom 4F. The tool is ready for any runbook or automation, and there's no service account key on anyone's laptop.

[Script tools](/product/script-tools)

Priya asks for the boardroom sharing she does by hand every week, and the Assistant turns it into a script tool on Google's Calendar API. Example data.

## Describe the offboarding, get the automation

Tell the Risotto Assistant what should happen when someone leaves, and it builds the automation and the trigger that starts it. Priya asks: when someone leaves in Rippling, move their calendar and Drive to their manager, suspend their Google account, sign them out and post in #it-offboarding. The Assistant builds Google Workspace offboarding on the Rippling employee terminated trigger. It looks up the manager in your identity provider, since Rippling's event doesn't name one, and sets approval to Destructive changes, so the transfer, the suspension and the sign-out wait for IT. It starts turned off and runs once Priya turns it on.

[Automations](/product/automations)

Priya describes the offboarding, and the Assistant builds the automation and its Rippling trigger. It stays off until she turns it on. Example data.

## The meeting nobody can edit

Risotto hears this one constantly: a recurring meeting still owned by someone who left, so nobody can move it, rename it or add a guest. Nina Rossi asks in #it-help whether Tom Becker can take over Design Crit Weekly, which Dana Reyes still owns. Risotto sees Dana's account is suspended and asks IT to move Dana's calendar to Tom. Priya approves, and Google runs the same Data Transfer the Admin console uses. Once it finishes, Tom owns the meeting, along with the rest of Dana's calendar, and can change it or hand it on.

[Risotto and Google Workspace](/integrations/google-workspace)

Nina can't change a meeting Dana still owns. After IT approves, Risotto moves Dana's calendar to Tom. Example data.

## Resets and group requests, in the thread

A forgotten password gets a temporary one from Risotto by direct message, changed at the next sign-in. A new phone gets 2-Step Verification reset so the employee can enroll again, and a lost laptop gets signed out of every session. Google Group requests follow each group's own rules: Risotto adds people to open groups right away and asks the owners and managers of the rest.

[The AI agent](/product/ai-agent)

Lena asks to join sales-leads@, a group that needs its managers' approval. Morgan approves, and Risotto adds her. Example data.

## Every Google change on your terms

Risotto's Google tools run on access you grant, one scope at a time, and each action leaves a record.

- **Your own OAuth client.** It lives in your Google Cloud project, and its ID and secret sit in Risotto's credential vault.
- **Read only to start.** Write access comes one scope at a time, when a published tool needs it and an admin approves.
- **Approval before a change.** Resets, suspensions, sign-outs and transfers wait for an approver by default. You choose which can run on their own.
- **Passwords stay private.** A temporary password goes by direct message, never into a channel.

[Security and trust](/security)

## Start from the library

Start from one of these and change it to fit. Open one to see every step and tool, or [browse the library](/library).

### Joining and leaving

Accounts on day one, and the handoff on the last.

- [Rippling new hire onboarding](/library/automations/rippling-new-hire-onboarding): create the Google Workspace account and add the department's group
- [BambooHR offboarding](/library/automations/bamboohr-termination-offboarding): suspend Google Workspace and move Drive files to the manager
- [Manager-requested offboarding](/library/runbooks/manager-requested-offboarding): a manager asks, IT approves, and Risotto suspends the account and moves the files

### An account at risk

Close the doors first, then tell security.

- [Google Workspace account lockdown](/library/script-tools/google-workspace-account-lockdown): revoke app access, require a new password and end every session in one approval
- [Suspended Okta account review](/library/automations/okta-suspended-account-review): sign the person out of Google Workspace and alert security
- [Suspected phishing report](/library/runbooks/suspected-phishing-report): reset the password and end sessions if they typed it in

## Frequently asked questions

### Can Risotto do the Google admin jobs we script today?

Yes. Risotto calls the same Google APIs your scripts do. Describe the job, or paste the command you run, into the Risotto Assistant, and it builds a script tool that makes that API call, which you can use in runbooks and automations. It runs on your Google Workspace connection, so nobody keeps a service account key on a laptop. [Script tools](/product/script-tools)

### Can Risotto transfer a departed employee's Google Calendar?

Yes. Risotto moves a departed user's calendar, Drive or both to a new owner with Google's Data Transfer API, the same transfer the Admin console runs. The events go to the new owner, and Google releases the rooms the old owner booked. Large transfers run in the background on Google and can take several hours. Each transfer waits for an approver by default.

### Can Risotto move one meeting to a new owner?

Yes, when its owner has left. Risotto moves the departed owner's calendar to the new owner, and the meeting comes with it, along with the rest of their events. Like the Admin console's Data Transfer, it moves whole calendars, not single events. Once the transfer finishes, the new owner can change the meeting or hand it on.

### Does Risotto need a Google service account or domain-wide delegation?

No. Risotto's Google Workspace tools connector runs on an OAuth client your company owns, with one consent from a Workspace admin: no service account key, no domain-wide delegation and no impersonation. Script tools and the built-in user tools, from password resets to data transfers, run on it. Two Google tools, Create Google Group and Move User to OU, use service account credentials. [Risotto and Google Workspace](/integrations/google-workspace)

### What Google admin role does Risotto need?

A delegated admin with directory access is enough. Each tool can do what the consenting admin's privileges allow: User Management for resets, suspensions and sign-outs, and Data Transfer for moving calendars and Drive. To reset or suspend another admin, a super admin gives the consent.

### Can the Assistant build Google Workspace automations?

Yes. Describe what should happen, for example "when someone leaves in Rippling, move their calendar and Drive to their manager and suspend their account", and the Risotto Assistant builds the automation and its trigger. It starts turned off, every create and turn-on shows an approval card, and you choose whether every action or only destructive changes wait for IT. [Automations](/product/automations)

## Hand Risotto your Google admin queue

[Book a demo](/demo)

Source: https://www.tryrisotto.com/solutions/google-workspace-management
