# Google and Microsoft connected accounts

Employers can connect a Gmail, Google Calendar, and Meet account, or an Outlook and Teams account, to Intervieux through a PKCE-protected OAuth flow, with the resulting credentials stored in an encrypted-at-rest table and disconnectable at any time.

Interview scheduling, video links, and email all eventually touch a calendar or an inbox somewhere. Connecting the actual account those live in means Intervieux can work with real calendar availability and send from a real inbox, instead of approximating both from inside its own system.

## What it does

Two providers are supported: Google, covering Gmail, Google Calendar, and Meet, and Microsoft, covering Outlook and Teams. Connecting either one runs through a standard OAuth authorization flow protected with PKCE and a single-use state parameter, the same pattern used elsewhere in the app for OAuth callbacks. Once connected, the resulting access credentials are written to a dedicated table that encrypts them at rest, a stricter storage model than the plain JSON storage used for some other integration connections in the app. Connecting, successfully connecting, and disconnecting are each logged as their own audit event.

## How it works

1. **Choose a provider** — Google, for Gmail, Calendar, and Meet, or Microsoft, for Outlook and Teams, each connect independently, an employer isn't limited to one or the other.
2. **Authorize through OAuth with PKCE** — The connect flow starts a standard OAuth authorization request against the chosen provider, protected by PKCE and a state value that can only be used once, closing off the usual class of OAuth callback replay issues.
3. **Credentials are stored encrypted** — The resulting access and refresh credentials are written into a dedicated table designed to encrypt them at rest, rather than sitting in a general-purpose integration table alongside less sensitive connection data.
4. **The connection becomes available to the agent and features that use it** — Once connected, the account's calendar and email capabilities are available to features and the employer AI agent's own Google Workspace and Microsoft 365 tool extensions, alongside its other extensions for pipeline, sourcing, scheduling, e-sign, and the email center.
5. **Disconnect at any time** — Removing a connected account is a direct action, and it's logged the same way connecting is, so there's a record of when access to a given Google or Microsoft account started and stopped.

## Two providers, covering the tools teams already use

Google covers Gmail, Google Calendar, and Meet. Microsoft covers Outlook and Teams. Between the two, most hiring teams' actual email and calendar stack is represented, rather than requiring a switch to a third tool just to connect.

## PKCE and single-use state, not a bare redirect

The OAuth callback flow uses the same PKCE and single-use-state protections the app applies to its other OAuth integrations, closing off the class of vulnerability where a captured authorization response could be replayed.

## Encrypted storage, specifically for this table

Connected-account credentials sit in a table built to encrypt them at rest, a deliberately stricter model than the plain JSON storage some other, less sensitive integration connections use in the app.

## Every state change is audited

Starting a connection, completing it, and disconnecting are each their own recorded event, so there's a clear trail of when a given Google or Microsoft account was linked to the employer account and when access ended.

## The callback route is the same pattern used elsewhere

Connected accounts share their OAuth callback shape with the app's other integration surfaces, a single-use state value and PKCE, rather than a one-off implementation written just for Google or Microsoft. That consistency means a fix to that shared pattern strengthens every integration built on it, not just this one.

## Who this is for

This is for an employer who wants Intervieux's scheduling, video links, and email features to work against a real Gmail or Outlook inbox and a real Google or Microsoft Calendar, instead of managing availability and email entirely inside a separate system disconnected from the tools the team already runs their day out of.

## Frequently asked questions

### Which providers can I connect?

Google, covering Gmail, Google Calendar, and Meet, and Microsoft, covering Outlook and Teams. Both can be connected independently.

### How are my Google or Microsoft credentials stored?

In a dedicated table that encrypts credentials at rest, separate from the general-purpose storage used for some other integration connections in the app.

### Can I disconnect a connected account?

Yes. Disconnecting is a direct action available at any time, and it's logged the same way connecting is, so there's a record of when the connection ended.

### Does the AI agent use these connected accounts?

Yes. The employer AI agent has Google Workspace and Microsoft 365 tool extensions among its roughly 16 tool extensions, which draw on a connected account once it's linked.

## Related pages

- [Interview scheduling and booking links](/features/interview-scheduling)
- [The hosted MCP server](/features/mcp-server)
- [Branded email center](/features/email-center)
- [Frequently asked questions](/faq)

## Connect your real inbox and calendar

Link Gmail and Google Calendar, or Outlook and Teams, so scheduling and email work against the tools your team already uses.

Start practicing free: https://www.intervieux.ai/register · Hire with Intervieux: https://www.intervieux.ai/employers/signup