Meeting
Gwinnett Global Methodist Church - Current
Gist
Chris did a technical support call with Charles Kirkman of Gwinnett Global Methodist Church to verify their new website domain (gwinnettgmc.org) was correctly configured on Cloudflare and pointing to their Church Track platform. They confirmed the DNS setup was correct and just needed time for Google to fully update search results away from the old churchtrack.com URL. They also reviewed Google Workspace MX/DKIM/SPF record setup for email, and discussed security practices like two-factor authentication and password/account continuity planning.
Distilled from the transcript by claude-sonnet-5 · Jul 25
What came out of it
Decisions2
- Confirmed the Gwinnett GMC website DNS setup on Cloudflare is correct and functioning properly
- Decided Charles will change the Cloudflare password after giving temporary access to the Google Workspace setup team
Risks and blockers3
- Google search results still show the old churchtrack.com URL alongside the new domain, which may take time to update
- Giving Google Workspace setup vendor access to Cloudflare account creates a security exposure until password is changed afterward
- Church currently has only one Cloudflare administrator, creating a business continuity risk
Open questions2
- Whether an A or quad-A record is actually needed for the Google Workspace MX setup
- Whether some existing DNS/TXT records from the old GoDaddy setup are extraneous and safe to remove
Next steps4
- ClientChange the Cloudflare account password after the Google Workspace vendor finishes setup
- ClientSet up two-factor authentication on the Cloudflare account
- ClientAdd a second administrator to the Cloudflare account for continuity
- VendorComplete Google Workspace MX/DKIM/SPF record setup
A record of what was agreed, not a task list — nothing here was scheduled.
From this meeting
No tasks spawned from this meeting.
Notes
No notes on this meeting yet. Use the plus Note button to add one.