fix(integrations): show family service accounts on every product they authenticate

[waleedlatif1]

Summary

• Adding a service account from the Jira page produced a credential that showed up under neither Jira, Jira Service Management, nor Confluence — it was titled "Atlassian Service Account", lost its brand tile, and disappeared from every category filter. The same bug hid a Google service account everywhere except Gmail.
• Root cause: one Atlassian token authenticates all three products, so it's modeled as an atlassian pseudo-provider. Display resolved through getServiceConfigByProviderId, which walks OAUTH_PROVIDERS in declaration order and therefore landed on that pseudo-service rather than on any product.
• Credentials now match via credentialProviderMatchesService (a service's OAuth id or its service-account id), so a family credential lists on every product it powers.
• New lib/integrations/credential-display.ts is the single resolver for catalog join, mark, and copy — replacing three duplicated lookups that keyed the catalog by OAuth service display name, which is exactly why the pseudo-service fell off the map.
• "Family service account" is derived from the catalog (a service-account id serving >1 integration), not a hardcoded vendor list, so a new integration joining a family needs no edit here.
• Service-account detail pages now title by credential name and subtitle with their reach; the connect form states that reach up front. Non-family credentials keep the service description they've always shown.
• Second commit swaps Jira/Confluence to Atlassian's gradient marks alongside a new Atlassian mark. Visual-only, but it renders in ~60 files, so it's split out to stay independently revertable.

Type of Change

• Bug fix

Testing

• Coverage for all 22 service-account provider ids is pinned in credential-display.test.ts. 19 are byte-identical to before; only atlassian-service-account (nowhere -> confluence/jira/jira-service-management) and google-service-account (gmail-only -> all 13) move, and both converge on what the block credential picker already shipped via getServiceAccountProviderForProviderId.
• A dedicated test asserts the index and the predicate the Connected list actually filters on cannot drift apart — verified it goes red when the fix is reverted, while the index-only tests stay green.
• Full suite: 16497 passed, 1 pre-existing environmental failure (cloud-review-tools.test.ts needs a real rg binary; this change touches no files under executor/).
• type-check, check:client-boundary, check:utils, check:bare-icons, check:icon-paths, check:api-validation, check:boundaries, check:react-query all pass.
• No schema, migration, contract, or persisted-value changes — resolution is computed at render time from static config, so pre-existing credentials behave identically to new ones.
• Not yet verified live — I don't have an Atlassian API token to mint a real service account, so the rendered result is unverified.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Jul 30, 2026 8:41pm

[cursor]

PR Summary

Medium Risk
Touches credential listing and matching across many integration UI surfaces; logic is well-tested but wrong matching would hide or mislabel production credentials.

Overview
Fixes family service accounts (one Atlassian token for Jira, Jira Service Management, and Confluence; one Google key for all Google integrations) disappearing from product integration pages after connect, and mislabeled as a single product.

Matching now uses credentialProviderMatchesService so a credential’s providerId can match a product’s OAuth id or its shared serviceAccountProviderId, instead of comparing resolved pseudo-service providerIds.

resolveCredentialDisplay in credential-display.ts centralizes catalog coverage, icons, subtitles, and detail copy so the integrations list, Cmd-K search, credential detail, and connect flows stay aligned. Family accounts show vendor identity (Atlassian / Google), corporate icons, and subtitles that spell out reach.

Connect surfaces use family name/icon via useServiceAccountConnectTarget; the Atlassian modal adds a catalog-derived coverage hint on the site domain field. Docs for Atlassian service accounts are updated for JSM and one-credential-across-three-products setup.

Includes Atlassian corporate icon and refreshed Jira/Confluence gradient marks (visual-only).

^{Reviewed by Cursor Bugbot for commit 14b5fa7. Configure here.}

[greptile-apps]

Greptile Summary

This PR centralizes credential presentation and broadens family service-account visibility across supported integrations.

• Adds a shared resolver for credential catalog matching, branding, titles, subtitles, and family coverage.
• Lists Atlassian and Google service accounts on every integration configured to accept their shared provider IDs.
• Uses family-level names and icons in service-account connection and reconnection surfaces.
• Updates Atlassian documentation and replaces Jira and Confluence marks with gradient variants.
• Adds regression coverage for all registered service-account provider IDs.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
apps/sim/lib/integrations/credential-display.ts	Introduces the shared, catalog-driven resolver for credential coverage, branding, and display copy.
apps/sim/lib/oauth/utils.ts	Adds exact matching against both a service's OAuth provider ID and service-account provider ID.
apps/sim/app/workspace/[workspaceId]/integrations/[block]/integration-block-detail.tsx	Uses the shared provider predicate so family credentials appear on each supported product page.
apps/sim/app/workspace/[workspaceId]/integrations/integrations.tsx	Migrates connected credential rendering and search metadata to the shared display resolver.
apps/sim/app/workspace/[workspaceId]/integrations/connected/[credentialId]/connected-credential-detail.tsx	Uses resolved family branding and credential-specific detail-page copy.
apps/sim/lib/integrations/credential-display.test.ts	Pins provider coverage and verifies display behavior for family, single-product, OAuth, and unresolved credentials.
apps/sim/components/icons.tsx	Adds the Atlassian corporate mark and updates Jira and Confluence SVG artwork.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Credential[Stored credential provider ID] --> Resolver[Credential display resolver]
  Resolver --> Registry[OAuth provider registry]
  Resolver --> Catalog[Integration catalog]
  Registry --> Match[Match OAuth or service-account provider ID]
  Catalog --> Coverage[Determine covered integrations]
  Match --> Display[Resolve family name and icon]
  Coverage --> Display
  Display --> List[Connected integrations list]
  Display --> Detail[Credential detail]
  Display --> Search[Integration search]
  Display --> Connect[Connect and reconnect modals]

Loading

_{Reviews (3): Last reviewed commit: "docs(atlassian): correct the service-acc..." | Re-trigger Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 14b5fa7. Configure here.}