The integrations hub#

Settings, Integrations is the one surface for every external connection Reportworq makes. If Reportworq needs to reach a data source, deliver to a destination, call an AI model, read source files, or authenticate users, that connection is registered and tested here. It is reached from the Integrations card on the Settings landing.

Connections are grouped into six families:

Each connection appears as a card with a name, an on/off status pill, and a context (three-dot) menu.

Note: the Authentication family used to be a Configuration tab. It moved here, so manage sign-in providers on this screen, not in Server configuration.

Before you begin#

• You need administrator rights.
• Have the credentials or endpoints for the connection you are adding ready (server names, API keys, service-account details).

Add a connection#

1. Open Settings, Integrations.
2. Select Add integration. A full-page catalog opens with a search box and grouped tiles.
3. Search for or scroll to the integration you want, then select Add on its tile.
4. Fill in the connection editor. Save stays disabled until you change something.
5. Where the connection supports it, select Test connection. A good connection reports Success.
6. Save.

Some integrations are singletons, they can be added only once. A singleton that is already configured (for example the active authentication provider) shows in the catalog as disabled with an Already added note and no Add button.

Edit, test, enable, or delete a connection#

Open a card's context (three-dot) menu for its actions:

• Edit opens the connection editor. As in the add flow, Save enables only once the editor is dirty.
• Test validates the connection and reports success or the error it hit.
• Enable / Disable toggles whether Reportworq uses the connection, without deleting it.
• Delete removes the connection.

The Platform, MCP Connection tool card has no context menu, it is a tool rather than a stored connection, and opens a full-screen editor.

Test everything at once#

Before a large scheduled batch, confirm every connection is reachable:

1. On the Integrations list, select Test all connections.
2. In the dialog, select Start. Reportworq tests each enabled, testable connection and reports the results.
3. Select Close when done.

Authentication providers have no test path, so they are not included. If no enabled testable connection exists, the action shows a "no enabled connections" notice instead.

Filter the list#

The header status filter narrows the list to All, Enabled, or Disabled. On All, every family group renders even when empty. On Enabled, groups with no enabled connections are hidden and only on-state cards show. When your account can reach more than one workspace, workspace-scoped families (such as Datasources) show a workspace-scope note.

Where to go for each family's detail#

The hub is where connections are registered. Each family's setup detail lives with the feature it powers:

• AI Connections, see Connect an AI provider.
• Datasources, see Connect a data source and the Connector catalog.
• Distributors, see Destinations.
• Report Providers, the source-file locations authors build reports from.
• Platform, MCP Connection, see Copilot, MCP, and trust paths.

Notes and limits#

• Instance-wide operational settings (web server, performance, logging, license) are in Server configuration, not here.
• Changing the active authentication provider warns that a service restart is required.
• Some connections are singletons and can be added only once.

Going deeper. For the full list of connectors and their per-connector authentication notes, see the Connector catalog.