Skip to content
Rival Enterprise

Connector governance & security

Connectors are where AI meets your real data, so they’re where governance matters most. This page covers how an organization keeps that boundary safe.

Approved connectors

Section titled “Approved connectors”

In the enterprise, not every connector is available to everyone. Admins decide which connectors are approved — available to be used — and which agents and team members can use each one. A team member can only connect the personal apps their admin permits. This keeps the set of doors into your data deliberately small and known.

Authentication

Section titled “Authentication”

Connectors use each system’s standard, scoped authentication, so Rival holds delegated access rather than raw credentials. Best practice is to connect shared systems at the organization level (not through an individual’s personal login), so access survives staff changes and is managed centrally.

Security best practices

Section titled “Security best practices”
  • Grant the minimum. Give each agent only the connectors it actually needs.
  • Prefer org-level connections for shared systems over personal ones.
  • Review access regularly — remove connectors and grants that are no longer used.
  • Watch the audit trail. Connector usage shows up in activity logs; use it. See Audit logs.

A quick example

Section titled “A quick example”

Finance connects an accounting system but approves it only for two vetted agents and no team-member personal use. If someone builds a new agent that wants that connector, they have to request it — and an admin decides. The sensitive system stays reachable by exactly what’s been vetted, and nothing else.