Feat: Add settings page with integration and relationship configuration (Phase 2) #241
+1,181
−8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add settings infrastructure for coach integration configuration and per-relationship AI privacy settings. This is Phase 2 of the AI Meeting Integration feature, building on the backend foundation from Phase 1.
GitHub Issue: Relates to #146
Changes
Settings Page & Routing:
/settingsroute with standard app layout (sidebar, header)SettingsContainerwith tabs for Integrations and RelationshipsIntegration Settings (Coach-only):
Relationship Settings (Coach-only):
Type Definitions:
AiPrivacyLevelenum to coaching-relationship typesmeeting_urlandai_privacy_leveltoCoachingRelationshipinterfaceUserIntegrationtypes for API credentials statusMeetingRecording,Transcription,TranscriptSegmenttypesAiSuggestedItemtypes for AI-suggested actions/agreementsAPI Updates:
user-integrationsAPI module with SWR hooksupdatemethod for meeting_url and ai_privacy_levelScreenshots / Videos Showing UI Changes (if applicable)
N/A - Backend API endpoints not yet implemented, UI will show loading/error states
Testing Strategy
npm run lint- passes with only one pre-existing warningnpx tsc --noEmit- passes with no errors/settingswhen logged in as a coach to see the settings pageConcerns
/oauth/google/authorizeendpoint which will be implemented in Phase 3.