Show disabled integration actions for members

Merged
RH
2mo ago
+395-56

Summary

Members could open integration creation flows even though the server rejected their writes. Keep restricted integration actions visible and disabled across the page header, empty state, sidebar, command palette, catalog, and Edit/Delete controls. Disabled controls explain that a workspace admin is required.

Members can browse the catalog, view existing integrations, and open personal connection setup. Catalog Add buttons, URL submission (including Enter), and setup shortcuts are disabled. Direct setup links explain the admin requirement. Admin creation and single-user access stay available.

Verification

  • bun run format:check
  • bun run lint
  • bun run typecheck — 45 tasks passed.
  • cd packages/react && bun run test — 49 files, 446 tests passed.
  • Cloud and self-host integration-creation-permissions.test.ts — both passed. Each creates an integration through the admin UI and verifies persisted state. Member checks cover visible disabled controls, the hover/focus explanation, command-palette entries, Edit/Delete, catalog Add buttons, URL submission, personal connection setup, and direct setup links.
  • Full unit suite passed in CI on this PR head (run).

Evidence

The member recording and screenshots show visible disabled controls, the admin tooltip, catalog browsing, and disabled Edit/Delete. All identities and integrations are synthetic.

Integration creation · self-host members see admin guidance and owners can add (selfhost)

00-member-sees-disabled-creation-controls-with-an-admin-explana.png

04-member-browses-the-catalog-with-disabled-add-buttons.png

02-member-sees-disabled-edit-and-delete-actions.png

Checklist

  • Added a changeset.
  • Added browser regression scenarios for cloud and self-host.
  • No secrets, credentials, or private data in the diff.