Skip to main content

Connector fleet

Connectors in the MSP Portal is the fleet view: every integration you run inside your clients' organizations, in one table, with its health, its last successful sync, and the evidence it feeds. A connector instance belongs to one client organization and to your partner, so a failing connector shows up here before the client notices missing evidence.

Catalog and instances​

The Catalog (the button at the top right of the fleet page) lists the connector types your partner supports: cloud providers, identity, EDR, vulnerability scanners, ticketing, MDM, SIEM, GRC, backup and DLP tools. Each entry declares the shape of its configuration and credentials, its default sync interval, the worker that runs the sync, and a link to its documentation where one exists. Entries are marked active, beta, deprecated or retired; only active and beta entries can be instantiated. The catalog is read-only in the portal today; SolveGRC seeds it for your partner.

An instance is one catalog entry deployed into one client. New Connector asks for the client, the catalog entry, a display name (for example "Acme Prod AWS"), an optional scope (JSON, such as an account id and regions) and optional non-secret configuration. The instance is created in pending config and stays there until credentials are saved.

The fleet table​

The summary row counts total, active, degraded and failing instances and how many clients have at least one failure. Below it, the table shows each instance with its client, status, last successful sync, consecutive failures and the last error. Search across connector, vendor and client names; sort by oldest or newest last success, most failures, client name, or status severity; toggle Failing only to work the problems.

Instance statuses: pending config (no credentials yet), active, degraded, failing, disabled (paused by an operator) and archived (kept for the record, no longer syncing, hidden from the fleet).

Working one instance​

Click a row to open the drawer. The header shows the status, the run of consecutive failures, and how many evidence items are blocked by this connector. Actions depend on state:

  • Re-sync now for a configured instance that is not disabled or archived. A sync triggered less than a minute after the last one is refused with a short wait.
  • Pause an active, degraded or failing instance; Resume a disabled one.
  • Archive stops syncing for good and removes the instance from the fleet; its configuration is kept.

Three tabs: Sync history lists each run with its trigger (scheduled, manual, bulk, rotation, or first sync), status (running, success, partial, failed, timed out, cancelled), items processed, evidence emitted, duration and any error. Credentials is where secrets go in. Config shows the sync interval, status and reason, next scheduled sync, scope and configuration, read-only.

Credentials​

The credentials form is generated from the catalog entry: each field it asks for is one the connector type declared, and required fields are marked. The first save configures the instance and moves it towards active; every later save is a rotation and asks for a reason (for example a scheduled 90-day rotation, a vendor disclosure, or a suspected compromise), which lands in the audit log.

Credentials are stored in a vault and are never shown in the portal again after saving. Only the sync workers read them, server-side. A rotation replaces the whole credential; leaving a field blank to keep its old value is not supported yet.

Bulk actions​

Select instances with the checkboxes and a bar appears at the bottom: Pause, Resume, Re-sync or Flag rotation, with an optional reason that is written to the audit log. A bulk action covers up to 100 instances at a time and reports how many were processed and how many skipped.

On the dashboard​

The MSP dashboard carries a Connector Fleet card with the same totals, a warning strip naming how many clients have failing connectors, and the category breakdown, with a link back to the fleet.