Issues / #74
iamnim org page: show selected shared drives and allow editing
proposed
improvement
Priority: medium
Project: iamnim
Reporter:
25 Mar 2026 20:27
Description
After Google Drive consent, the drive selection works but the org page (`/organizations/{slug}`) does not show which drives are currently selected or allow changing the selection.
**Current behavior:**
- Connect Google Drive → consent → drive selection page → saves to Pantheon
- Org page just shows "Connected" with a disconnect button
- No way to see or edit which drives are synced
**Expected behavior:**
- Org page shows the names of selected shared drives under the Google Drive integration
- An "Edit drives" button opens the drive selection page (re-uses existing template)
- This requires fetching the integration config from Pantheon and resolving drive IDs to names (either cached in config or fetched via Drive API with the stored token)
**Files:**
- `iamnim/internal/web/templates/organization.html` — show selected drives
- `iamnim/internal/web/server.go` — handleOrganization needs to parse integration config
- `iamnim/internal/web/google_drive.go` — add route for editing drives without re-consent
**Current behavior:**
- Connect Google Drive → consent → drive selection page → saves to Pantheon
- Org page just shows "Connected" with a disconnect button
- No way to see or edit which drives are synced
**Expected behavior:**
- Org page shows the names of selected shared drives under the Google Drive integration
- An "Edit drives" button opens the drive selection page (re-uses existing template)
- This requires fetching the integration config from Pantheon and resolving drive IDs to names (either cached in config or fetched via Drive API with the stored token)
**Files:**
- `iamnim/internal/web/templates/organization.html` — show selected drives
- `iamnim/internal/web/server.go` — handleOrganization needs to parse integration config
- `iamnim/internal/web/google_drive.go` — add route for editing drives without re-consent
Comments (1)
nebula
25 Mar 2026 20:30
Grooming: set priority to medium
Nebula's reasoning: This is a UX completeness issue — the core Google Drive integration works (consent, selection, saving), but users lose visibility into their configuration after the initial setup. Medium priority because it's not blocking any workflow but creates a dead-end experience where users can't verify or change their drive selection without disconnecting and reconnecting. Title and description are already clear and well-structured, no cleanup needed.
Nebula's reasoning: This is a UX completeness issue — the core Google Drive integration works (consent, selection, saving), but users lose visibility into their configuration after the initial setup. Medium priority because it's not blocking any workflow but creates a dead-end experience where users can't verify or change their drive selection without disconnecting and reconnecting. Title and description are already clear and well-structured, no cleanup needed.