---
title: Staging Site Gmail Integration Blocker
type: article
created: '2025-10-06'
updated: '2025-10-06'
source_docs:
- raw/2025-10-06-team-stand-up-92005381.md
tags:
- blocker
- lammary
- staging
- gmail
- google-integration
- bookly
- technical
layer: 2
client_source: LaMarie Beauty
industry_context: ecommerce
transferable: false
---

# Staging Site Gmail Integration Blocker

## Overview

During the 2025-10-06 team standup, Chris flagged a technical blocker on the Lammary project: the staging site's domain does not match the production domain, which prevents Gmail/Google OAuth from authorizing the connection. This blocks all integration testing for the Bookly booking system, including the Bookly ↔ Square integration.

## The Problem

Google's OAuth flow validates the requesting domain against the authorized redirect URIs registered in the Google/G Suite account. Because the staging environment uses a different domain (not matching Lammary's production domain), Google refuses the connection entirely.

> "My suspicion is that I'm unable to connect to the Gmail stuff because it sends a query from the staging site… that doesn't match their URL, so their domain name, which means I'm not even allowed to connect anything."
> — Chris Østergaard, standup 2025-10-06

As a result, Chris cannot test:
- Gmail / Google integration
- Bookly ↔ Square integration
- Any other OAuth-dependent feature

## Additional Concern: Bookly Hidden Costs

Chris also noted that Bookly has been accumulating unexpected costs — additional features are gated behind add-on fees (~$50/month each). This was flagged as a growing concern given the scope of the project proposal.

## Proposed Solutions

| Approach | Notes |
|---|---|
| **Dummy domain / live test environment** | Create a separate live domain with its own G Suite account to mirror the production setup. Allows full integration testing without touching the client's live site. Discussed by Mark as the likely path forward. |
| **Test on live site** | Possible but risks disrupting Lammary's day-to-day operations. Not preferred. |

Mark agreed to think through the dummy domain approach and follow up with Chris.

## Status

- **Blocker raised:** 2025-10-06
- **Owner:** Chris Østergaard
- **Escalated to:** Mark Hope (for solution design)
- **Resolution:** Pending — Mark to advise on dummy domain / test environment setup

## Action Items

- [ ] **Mark** → Determine feasibility of dummy domain/G Suite test environment and advise Chris
- [ ] **Chris** → Implement agreed testing approach once direction is confirmed; resume Bookly + Gmail/Google integration work

## Related

- [[wiki/clients/current/lamarie/_index]]
- [[wiki/meetings/2025-10-06-team-standup]]