From 42188eecf08a246f150e8929fde1dd8f153aaa1b Mon Sep 17 00:00:00 2001
From: happybell80 <goeun2dcc@gmail.com>
Date: Wed, 17 Sep 2025 21:29:15 +0900
Subject: [PATCH] Update DB schema for two-phase implementation plan

Phase 1: Login only with existing user table
Phase 2: Passport with workspace and token tables for API access
---
 ...0916_네이버웍스_캘린더_API_연동_가이드.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/ideas/250916_네이버웍스_캘린더_API_연동_가이드.md b/ideas/250916_네이버웍스_캘린더_API_연동_가이드.md
index d927d37..bc0aade 100644
--- a/ideas/250916_네이버웍스_캘린더_API_연동_가이드.md
+++ b/ideas/250916_네이버웍스_캘린더_API_연동_가이드.md
@@ -159,15 +159,15 @@
 - **`nginx-infra`**: `/auth/naverworks`, `/api/naverworks` 라우팅 설정
 
 #### DB 스키마
-- **로그인만 구현 (Phase 1)**:
+- **Phase 1: 로그인 구현** (현재):
   - 기존 `user` 테이블만 사용
   - oauth_provider="naverworks"
   - oauth_id={userinfo.sub}
-  - 신규 테이블 불필요
 
-- **API 사용시 추가 필요 (Phase 2)**:
-  - `team.naverworks_workspace`: Workspace 정보
+- **Phase 2: Passport 구현** (다음):
+  - `team.naverworks_workspace`: Workspace 정보 저장
   - `team.naverworks_token`: access_token/refresh_token 저장
+  - 메일/캘린더 API 접근용
 
 ### 5.2 구현 플로우 (Slack 패턴 참조)