From 4e82d17342e93c73d4fce65c96a3f14a398d9eb8 Mon Sep 17 00:00:00 2001
From: happybell80 <goeun2dcc@gmail.com>
Date: Wed, 17 Sep 2025 21:18:35 +0900
Subject: [PATCH] Clarify DB schema requirements for NAVER WORKS OAuth

- Add naverworks_workspace table requirement
- Clarify token storage necessity (only for API usage)
- Note difference between login-only vs API usage scenarios
---
 .../250916_네이버웍스_캘린더_API_연동_가이드.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/ideas/250916_네이버웍스_캘린더_API_연동_가이드.md b/ideas/250916_네이버웍스_캘린더_API_연동_가이드.md
index f902832..9f39867 100644
--- a/ideas/250916_네이버웍스_캘린더_API_연동_가이드.md
+++ b/ideas/250916_네이버웍스_캘린더_API_연동_가이드.md
@@ -161,7 +161,10 @@
 - **기존 user 테이블 활용** (SQLAlchemy: `__tablename__ = "user"`):
   - oauth_provider="naverworks"
   - oauth_id={NAVER WORKS userId}
-- **신규 테이블**: `team.naverworks_token` (Service Account 토큰 저장용)
+- **신규 테이블 필요**:
+  - `team.naverworks_workspace`: Workspace 정보 (Slack 패턴과 동일)
+  - `team.naverworks_token`: OIDC access_token/refresh_token 저장 (API 호출시 필수)
+  - 주의: 로그인만 할 경우 토큰 저장 불필요, API 사용시 필수
 
 ### 5.2 구현 플로우 (Slack 패턴 참조)