One club. Connected records.
Membership comes from the Google CRM. Portal responses and profile updates stay safely queued until Google confirms receipt.
Connection status
Sync imports the private membership roster and sends up to 20 member updates and 20 attendance records per manual sync. It sends no emails. Profile changes are staged for board review; RSVP records are separate from verified attendance.
A record we can return to.
Scheduled syncs keep membership connected. Recovery copies protect the club’s records and photographs.
Retention: 48 hourly portal snapshots, 30 daily recovery sets and 12 monthly recovery sets. Photo archives are retained separately. Private Drive copies and independent workbook archives provide recovery across both services. A backup is marked complete only after its saved files have been checked.
What syncs, and where
The Google roster controls membership eligibility. The portal sends RSVPs, profile details and private feedback to dedicated Google tabs. Contact changes await board review. New board-recorded attendance goes to Tavern Attendance in the sandbox. Present records also feed its Attendance Log and reports; correcting someone to absent removes only that portal-owned report row. Existing CRM attendance is preserved and any overlap requires review. Attendance transfer to the master CRM remains disabled. Conversations and photographs remain in the portal. Direct edits to Google RSVP or feedback tabs do not replace portal records.
Automatic sync is scheduled for every 15 minutes; provider delays can affect timing. Nightly recovery runs around 3 a.m. Eastern. Warnings above reflect actual recorded success, not just the planned schedule.
Google activation
The one-time Google deployment and authorization are still required. The prepared bridge uses a signed server connection. Member contacts are never placed in the public website files.
Create a separate Apps Script project using the prepared bridge below. Its write destination starts in the existing CRM sandbox. The current receipt and email scripts stay intact.
Download prepared Google bridge- Add the bridge code to a new standalone Apps Script project.
- Set its BRIDGE_SECRET script property, run setupTavernBridge and authorize Google.
- Deploy as a web app. The same secret and deployment URL must be configured in the portal’s server settings.
- Return here to verify the roster and sandbox sync before enabling master CRM writes.