Connect Google Calendar: reminders where your team already looks

How do I connect Google Calendar?

The connection lives in Settings, under Integrations. An account owner can connect it, and so can an admin with permission to manage calendar connections. Both need multi-factor authentication completed first, the same bar FlockConnect sets for other sensitive settings.

When you click connect, FlockConnect sends you to Google's own consent screen. You sign in with Google, on Google's site, and review what is being requested before you approve it. Your Google password never passes through FlockConnect. After you approve, Google sends you back to the Integrations page, which shows the connection status.

• An account owner, or an admin with the calendar connections permission, connects and disconnects. Multi-factor authentication is required.
• You approve the connection on Google's own consent screen; your Google password never passes through FlockConnect.
• Writes only person-approved reminders with generic text and a secure link, never pastoral details.
• Reads only your list of calendars for the destination picker; the events already on them are never opened or imported.
• Supports personal, shared church, and shared team destination calendars, each verified for write access before use.
• Disconnecting clears the stored credential immediately and pauses your destinations until you reconnect.

What does FlockConnect write to my calendar?

Only follow-up reminders that a person has reviewed and approved. FlockConnect drafts a reminder, you approve it, and the approved reminder becomes a calendar event. The event text is generic and localized: a title reads something like "FlockConnect follow-up" or "Care team reminder," and the description is a short line with a secure link back into FlockConnect, where the real context lives behind a sign-in.

No names of who is being cared for, no notes, no prayer details, and no assessment answers appear in the event. There is one other small write: when you add a destination calendar, FlockConnect proves it can actually write there by creating a tiny private placeholder event and removing it right away. If you ever catch a glimpse of one, it is safe to ignore.

FlockConnect also updates or clears the reminder events it created when a follow-up changes or is completed, so stale reminders do not pile up on your team's week. It never touches events it did not create.

What does FlockConnect read from Google?

The consent screen asks Google for two things: permission to manage calendar events, which FlockConnect uses to create, update, and clear the reminders it wrote, and read access to your calendars, which it uses to show your calendars by name when you pick a destination.

That is the whole read path. FlockConnect does not open, import, store, or analyze the events already on your calendar. Your existing appointments stay yours, and nothing about them flows into FlockConnect.

What are shared destination calendars?

A destination is the calendar a reminder lands on. It can be personal, writing to one staff member's own Google calendar, or shared, writing to a church or team calendar the whole team watches, so a visit or a call does not rest on one person's memory.

Before a destination is used, FlockConnect verifies it can write there. If write access is missing, the destination is not used, and an owner or admin can see the problem in Integration Health on the same settings page. Because every event uses the same generic text, sharing a calendar widely never exposes who is being cared for.

How do I disconnect, and what happens then?

Disconnect from the same Integrations page, with the same owner-or-permitted-admin and multi-factor requirements as connecting. The stored Google credential is cleared immediately, so FlockConnect can no longer write to, update, or clear anything on your calendar.

Your destination settings are kept but paused, so reconnecting later restores them without rebuilding. Reminder events already on the calendar stay there; since FlockConnect can no longer clear them after a disconnect, remove any leftovers by hand if you want them gone. And if your church ever deletes its FlockConnect account entirely, the deletion process revokes the Google credential FlockConnect held as one of its steps.

How is the calendar credential handled?

FlockConnect keeps the Google credential on the server only. It is never sent to your browser, and it is never included in workspace exports. The connection uses OAuth, the standard way to grant an app limited access without sharing your password, and you can withdraw that access at any time by disconnecting.

How integration credentials are protected at rest, and how every connected service is held to the same bar, is covered on our Trust and Security page.