Skip to content
Rival Enterprise

Connecting your systems

Connecting a system makes it available for agents and workflows to use — under the governance your organization sets. Most connections follow the same shape: authorize Rival to access the system, confirm the scope, and the connector is live.

The general flow

Section titled “The general flow”
  1. Open Connectors and choose the system you want to connect.
  2. Authenticate — usually by signing in to that system and approving the access Rival requests.
  3. Confirm the scope (what Rival is allowed to see and do).
  4. The connector is now available to be granted to agents and users.

Common connectors

Section titled “Common connectors”

Slack — connect to let agents read and post in approved channels: digests, alerts, and workflow notifications. [VERIFY: confirm supported Slack scopes.]

Microsoft 365 — connect email, calendar, and files so agents can work across your Microsoft environment. [VERIFY: confirm which M365 services are supported.]

Google Workspace — connect Gmail, Calendar, and Drive for the Google equivalent. [VERIFY: confirm supported Workspace services.]

Salesforce — connect your CRM so agents can read and update records under approval. [VERIFY: confirm read vs. write scopes.]

Authentication

Section titled “Authentication”

Connectors authenticate through each system’s standard, secure sign-in — Rival receives scoped access, not your passwords. Admins should connect shared, business-critical systems at the organization level so access is managed centrally rather than tied to one person’s account.

A quick example

Section titled “A quick example”

An admin connects the company Slack workspace and grants the connector to the support team’s agents. Now those agents can post ticket summaries to a support channel — and only that team’s approved agents can use the connection.