# Tee Time Master — Integrations ## Purpose This document tells Oblive which business systems we use, what each system is authoritative for, and what access boundaries apply. It does not contain credentials, tokens, connection status, or secret values. This inventory describes the business systems known during onboarding. It is not a current connection report: a system may be used outside Oblive, and a connector installed later is reviewed against this evidence without rewriting the source. ## Integration Inventory | Integration | Primary Business Use | Authoritative For | Department Owners | Oblive May | Human Approval Required For | | ------------------------------------ | -------------------------------------------------------------------- | ------------------------------------------------------------- | --------------------------------- | --------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | | Stripe | Service-fee collection, payment verification, refunds, disputes | Charge, payment, refund, and dispute status | Organization, Support | Read payment state, reconcile records, prepare refund decisions | Charging outside the normal product flow, refunds, credits, write-offs, or dispute responses | | PostHog | Product, funnel, campaign, and experiment analytics | Defined product events and dashboards | Organization, Growth, Engineering | Read and analyze approved events and reports | New tracking involving sensitive data or changes to production instrumentation | | Google Apps Script and Google Sheets | Public waitlist intake and raw lead register | Original waitlist submissions | Growth | Read, validate, deduplicate, and segment submissions | Editing original submissions, sending outreach, or changing the collection form | | HubSpot | Launch CRM and qualified course-demand segments | Lead qualification, lifecycle stage, and campaign eligibility | Growth | Read and prepare updates to qualified lead records | Bulk record changes, lifecycle automation, or outbound enrollment | | SendGrid | Transactional and consent-based email | Email delivery and suppression evidence | Growth, Support | Inspect delivery state and prepare fully rendered messages | Sending, changing templates used in production, or overriding suppression and consent rules | | Twilio | Opted-in booking and service SMS | SMS delivery and opt-out evidence | Support | Inspect delivery and opt-out state and prepare approved messages | Sending SMS or changing consent and messaging configuration | | Meta | Website conversion measurement and approved paid acquisition | Campaign delivery and spend for Meta campaigns | Growth | Analyze approved campaign performance and prepare campaigns | Publishing, changing audience or claims, or starting and increasing spend | | Help Scout | Customer inbox and case ownership | Original customer thread, assigned owner, and support status | Support | Read threads, investigate, and stage replies on the original thread | Sending replies, changing customer state, or closing a sensitive case | | Notion | Policies, roadmap, decisions, experiment history, and knowledge base | Approved operating documents | Organization and all departments | Read approved documents and prepare updates for review | Replacing approved policy, publishing a new policy, or changing a consequential decision | | GitHub | Source control, pull requests, releases, and technical issues | Code and technical delivery history | Engineering | Read code and issues, create branches, prepare changes, and open review artifacts | Merging protected changes, deploying, changing repository controls, or exposing secrets | | Sentry | Production error tracking and incident evidence | Error events and grouped production failures | Engineering | Read and analyze errors and correlate incidents | Changing production alerting or deleting incident evidence | | Cloud hosting platform | Application deployment, runtime health, and managed secrets | Deployment state and service health | Engineering | Read health and prepare deployment or rollback plans | Deploying, rolling back, changing secrets, changing scale, or performing production writes | | Booking-egress provider | Controlled access to supported course-booking systems | Booking-network execution evidence | Engineering | Read health and investigate adapter outcomes | Enabling a course, changing routing, or bypassing a course control | ## Credential Rules - Credentials are connected through the approved integration setup flow, never pasted into these documents. - Each integration uses the least privilege needed for its documented business functions. - Read access and consequential write access are treated separately. - Production credentials are not reused in local development or test fixtures. - Secrets are never copied into chat, tickets, source code, analytics, or logs. - Revoked, expired, or mismatched access stops the affected workflow; it does not trigger a silent switch to another account or provider. ## Data Minimization - Use the internal customer UUID as the durable join key. - Email and phone are lookup and communication attributes, not cross-system primary keys. - Do not copy course credentials, authentication material, full payment details, or unnecessary customer data between systems. - Reports use aggregated data unless an individual record is required to resolve a specific case. - Exports and deletions require verified identity, a defined scope, and human approval. ## Connection Readiness Checklist Before an integration is used in a live workflow, its owner confirms: - the intended account and workspace; - the source-of-truth responsibility; - the minimum required permissions; - allowed read and write operations; - who approves consequential actions; - expected identifiers for joining records; - error, retry, and escalation behavior; - data retention and logging expectations; and - how access is revoked during an incident or offboarding. ## Integration Ownership | Department | First-Line Integrations | Escalation Owner | | ------------ | --------------------------------------------------------------- | ---------------- | | Organization | Stripe, PostHog, Notion | Joshua Bing | | Growth | Google Sheets, HubSpot, SendGrid, Meta, PostHog | Joshua Bing | | Engineering | GitHub, Sentry, cloud hosting, booking egress, PostHog | Joshua Bing | | Support | Help Scout, production customer state, SendGrid, Twilio, Stripe | Joshua Bing | Department-specific use appears in the corresponding department document. Cross-functional process rules appear in [Organization Workflows](workflows.md).