Gmail integration discussion

Jun 18, 11:08 AM · processed · project · lukas@own3d.tv

Summary

  • Discussed Gmail integration for the company memory.
  • Rejected full mailbox sync due to privacy and trust concerns.
  • Decided on explicit Gmail thread capture (labels/forwarding) for the MVP.
  • Raw email content to remain restricted.
  • Sarah to define minimum OAuth scopes; per-thread visibility controls remain an open question.

Lukas and Sarah discussed how to approach Gmail integration for the company memory. Sarah raised concerns that importing everyone's full mailbox would be a privacy issue, and Lukas agreed that full mailbox sync would create too much noise and trust issues with the team. They aligned on starting with explicit capture only, using labels or forwarding, while keeping raw email content restricted. Lukas recorded the decision to use explicit Gmail thread capture instead of full sync for the MVP. Sarah committed to defining the minimum OAuth scopes before implementation begins. Lukas noted an open question about whether per-thread visibility controls would also be needed.

What changed: The team decided to implement explicit Gmail thread capture (via labels or forwarding) for the MVP rather than full mailbox sync, with raw email content kept restricted.

Decisions

Explicit Gmail thread capture for MVPdraftrestricted · conf 0.90
For the MVP, the company memory will use explicit Gmail thread capture (via labels or forwarding) instead of full mailbox sync.

Action points

Define minimum OAuth scopesdraftrestricted · conf 0.90
Define the minimum OAuth scopes required before implementing the Gmail integration.

Risks

Full mailbox sync privacy and trust concernsdraftrestricted · conf 0.80
Full mailbox sync was identified as creating excessive noise and raising privacy and team trust concerns; avoided in favor of explicit capture.

Open questions

Per-thread visibility controlsdraftrestricted · conf 0.70
Whether per-thread visibility controls are needed for the Gmail integration.

Facts

Raw email content restricteddraftrestricted · conf 0.85
Raw email content is to be treated as restricted within the company memory system.

Entities mentioned

Gmail integrationCompany memoryGmailOAuthLukasSarah

Transcript

Lukas: Let's talk about Gmail integration for the company memory.
Sarah: I don't think we should import everyone's mailbox. That's a privacy nightmare.
Lukas: Agreed. Full mailbox sync creates too much noise and trust issues with the team.
Sarah: So we start with explicit capture only — labels or forwarding. Raw email content stays restricted.
Lukas: Decision then: explicit Gmail thread capture instead of full sync for the MVP.
Sarah: I'll define the minimum OAuth scopes before we implement anything.
Lukas: Good. Open question is whether we also need per-thread visibility controls.