{"slug":"connectors/09_CONNECTOR_MARKETPLACE_AND_INTEGRATION_REGISTRY_UI","title":"09 — Connector Marketplace and Integration Registry UI","section":"connectors","sectionLabel":"Connectors","status":"current","type":"document","path":"connectors/09_CONNECTOR_MARKETPLACE_AND_INTEGRATION_REGISTRY_UI.mdx","bytes":2282,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Active frontend handoff\n\n## Boundary\n\nThe Connector Marketplace is the tenant selection tray. Integration Manager is\nthe operational view of installed bindings, sync, webhooks and schemas. Neither\nsurface owns OAuth credentials or connector execution.\n\nThis in-product tray is distinct from the **IW-Spine-Network Plugin** published\nin plugin marketplaces and **IW-Spine-Network MCP** published in MCP\nmarketplaces. Those packages activate IntegrateWise; this tray adds provider\nconnections after activation.\n\n## Catalog view\n\nEach catalog item displays:\n\n- connector/package ID, name, publisher, category and verified version;\n- supported entities, read/write/webhook capabilities and required scopes;\n- supported environments and authorization method;\n- availability for the current role/industry/department projection;\n- install, configured, syncing, operational, degraded or revoked state.\n\nNo connector is hardcoded as mandatory infrastructure for customer tenants.\nConfiguration Manager and Activation Hub determine recommendations and\nreadiness.\n\n## Gateway interactions\n\nThe typed client uses the Gateway routes defined by the live contract, including\nworkspace discovery and marketplace package/installation endpoints. Authorization\nstarts through a Gateway-generated state/PKCE transaction. The browser never\nreceives provider refresh tokens.\n\nEvery installation is bound to:\n\n```text\ntenant_id + account_id + user_id + spine_network_id\n+ marketplace_package_id + provider_connection_id + environment\n```\n\n## Duplicate-source handling\n\nWhen the same provider/account is discovered through multiple hosts, show one\nlogical source with multiple bindings. The UI exposes provenance and lets an\nauthorized user choose precedence, merge policy or isolation. It must not merge\nrecords solely because provider names match.\n\n## Acceptance\n\n- Cross-tenant installations never appear.\n- Consent state survives redirect and is idempotent.\n- Revocation removes usable authority without deleting canonical history.\n- Partial discovery shows which hosts were searched and which failed.\n- A successful install does not display “operational” until activation and\n  initial synchronization evidence are complete.\n"}