Google

Google Accounts

Connect Google once to unlock Calendar, Drive, Groups, and meeting notes.

See it in action
At a glance

One connection powers every Google feature in Team Toolbox. Run /google connect to link your account, and Calendar events, Drive previews and search, Google Groups, and voice-meeting notes all start working.

All Users

Connect Google

Connecting links your own Google account. It uses OAuth, so Team Toolbox never sees your password, only the access the Google features need. Run /google connect in any channel, follow the secure link Team Toolbox sends you, and approve access on Google's consent screen. You can also connect or disconnect from your User Settings. Reconnect any time by running /google connect again; to revoke access, remove Team Toolbox from your Google account permissions.

Already covered by your team?

If your server admin connected your whole team (see the Server Admins section below), you're connected already and don't need to run anything.

/google connectLink or refresh your Google account.
/google helpA quick refresher plus a link back to these docs.

What you unlock

One connection covers the whole Google suite. Each feature has its own page with the details:

CalendarGoogle Calendar -- event notifications and RSVPs in a channel.
DriveGoogle Drive -- rich link previews and file search from chat.
GroupsGoogle Groups -- keep group membership in sync with Discord roles.
MeetingsVoice Meetings -- save transcripts and notes to a Google Doc.
Server Admins

Workspace Mode

Workspace Mode connects your team's Google Workspace once, for everyone. Nobody runs /google connect, nobody sees a Google sign-in screen — Calendar, Drive, and meeting notes just work for every member, and it's what lets Discord roles keep Google Groups in sync. You set it up once and then forget about it.

Before you start

You need a Google Workspace (a paid Google plan for your own domain, not a personal Gmail) and an admin account on it. If your team is on personal Gmail accounts, skip this — everyone connects individually instead, which works fine.

1. Turn it on and sign in

Open Server Settings, expand Google Accounts, and switch on Workspace Mode. Google will ask you to sign in — use your Workspace admin account. That sign-in is only there so Google can confirm which Workspace you manage; it doesn't hand over your mail or files.

When you come back, the panel shows the account you signed in with and two values you'll need next.

2. Let Google know Team Toolbox is allowed

Google won't let an app act for your team until you say so. Open Domain-wide delegation in the Google Admin console (Security › Access and data control › API controls if you'd rather click through), then choose Add new.

It asks for two things. Copy them from here, or from the same two boxes on the Server Settings panel:

Client ID
104568748281088972893

Identifies Team Toolbox to Google. It's the only value that goes in that box.

OAuth scopes
https://www.googleapis.com/auth/userinfo.profile,https://www.googleapis.com/auth/userinfo.email,https://www.googleapis.com/auth/drive,https://www.googleapis.com/auth/calendar,https://www.googleapis.com/auth/documents,https://www.googleapis.com/auth/admin.directory.user.readonly,https://www.googleapis.com/auth/admin.directory.notifications,https://www.googleapis.com/auth/admin.directory.group,https://www.googleapis.com/auth/admin.directory.group.member,openid

The list of things Team Toolbox may do. Paste all of it in one go, commas and all.

Hit Authorize, and Google starts trusting Team Toolbox for your domain.

3. Check it worked

Back on the Google Accounts panel, hit Check again. A green banner means you're done and your whole team is covered. If it's still amber, the values from step 2 usually just haven't saved on Google's side yet — give it a minute and check once more.

Once it's working, the setup steps fold away and the panel just tells you which account it's connected through. You don't have to keep an eye on it either: if Workspace Mode ever stops working later, this same panel says so, and members quietly fall back to connecting their own accounts in the meantime.

4. Tell Google who's who in Discord

One last piece: Google needs a way to tell that a Discord member is the same person as a Workspace account. You give it somewhere to record that, then fill it in per person.

Open Manage custom attributes and add an attribute with the category Discord and a field called User ID, set to Whole Number and visible to everyone in your organization.

Then, for each person, open their profile under Directory › Users, edit their user information, and paste their Discord ID into that field. To get someone's ID: turn on Developer Mode in Discord's settings, right-click them, and choose Copy User ID. Members don't have to do anything themselves, and access follows along whenever you update it.

You don't have to keep track of who you've done, either. The Google Accounts panel lists everyone in the server who still hasn't got a Discord ID on their Google profile, with a button to copy each ID and a link straight to the Admin console. Anyone on that list keeps working, they just connect their own Google account with /google connect until you fill their ID in.

Steps 2 and 4 need a Google Super Admin

Only a Super Admin on your Workspace can allow an app or edit user attributes. If that's not you, the person who handles your Google accounts can do those two parts — it's a one-time job.

Need a hand?

Run /google help in Discord, join the community server, or check the Help page.