Move Integrations into the Settings menu and remove the redundant integrations button #91

New issue

Closed

opened 2026-06-30 12:51:25 -05:00 by Gitchegumi · 0 comments

Gitchegumi commented

2026-06-30 12:51:25 -05:00

(Migrated from github.com)

Problem

The current Settings experience treats integrations as a separate destination reached by a button from the Settings page. That is poor information architecture: integrations are settings and should live directly in the Settings menu/navigation.

The extra button is especially bad because it appears below the Danger Zone. Nothing non-destructive should be buried under destructive-account/system actions.

Expected behavior

Integrations should be a first-class Settings section, not a separate button buried on the Settings landing page.

Acceptance criteria

Add Integrations directly to the Settings menu/navigation alongside the other settings sections.
Keep /dashboard/settings/integrations as the canonical integrations route unless there is a better existing route convention.
Remove the redundant integrations button/link from the Settings landing page.
Ensure no non-danger navigation appears below the Danger Zone.
Danger Zone should remain visually and structurally last.
Update active-route styling so the Settings menu clearly indicates when the user is on Integrations.
Add or update tests for Settings navigation if coverage exists for that area.

Notes

Complete refactors are acceptable here. The UX should be cleaned up rather than patched around the current awkward button placement.

## Problem The current Settings experience treats integrations as a separate destination reached by a button from the Settings page. That is poor information architecture: integrations are settings and should live directly in the Settings menu/navigation. The extra button is especially bad because it appears below the Danger Zone. Nothing non-destructive should be buried under destructive-account/system actions. ## Expected behavior Integrations should be a first-class Settings section, not a separate button buried on the Settings landing page. ## Acceptance criteria - Add `Integrations` directly to the Settings menu/navigation alongside the other settings sections. - Keep `/dashboard/settings/integrations` as the canonical integrations route unless there is a better existing route convention. - Remove the redundant integrations button/link from the Settings landing page. - Ensure no non-danger navigation appears below the Danger Zone. - Danger Zone should remain visually and structurally last. - Update active-route styling so the Settings menu clearly indicates when the user is on Integrations. - Add or update tests for Settings navigation if coverage exists for that area. ## Notes Complete refactors are acceptable here. The UX should be cleaned up rather than patched around the current awkward button placement.

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gitchegumi/GitchAlerts#91

No description provided.

Rows
Columns