Connectors

Connectors are shared controls for tools that can affect your workspace, project, backend, payments, or generated app behavior.

They are designed for governance first.

What a connector is

A connector usually includes:

• A dashboard catalog entry.
• Workspace default settings.
• Optional project overrides.
• Capability-level permissions.
• Clear controls for sensitive actions.

Current connector policies use three modes:

Mode	Use it when
Allow	The capability is routine and approved for the team.
Ask	The capability is useful but should be confirmed each time.
Deny	The capability is not allowed for this workspace or project.

Current connector catalog

The current catalog includes:

Connector	What it is for
RIB Cloud	Built-in backend capabilities such as database, auth, storage, project information, cloud logs, and security checks.
Stripe	Payment governance for generated apps that use the project owner's own Stripe account.

Not every integration is a connector. GitHub sync is managed through GitHub settings and project settings, not through the connector catalog today.

Workspace defaults and project overrides

Workspace connector settings define the default policy.

A project can inherit those defaults or use a project-specific override when the product exposes that control. This is useful when one project needs tighter rules than the rest of the workspace.

Owners and admins can manage connector policies. Members can use capabilities that are available to them, but they should not assume they can change workspace defaults.

RIB Cloud connector

RIB Cloud controls project backend capabilities.

Depending on your workspace policy, it can cover:

• Reading database structure or records.
• Reading analytics or project information.
• Running security checks.
• Modifying database structure or records.
• Adding seed data.
• Configuring auth.
• Reading backend logs.
• Choosing the default hosting region for new cloud resources.

Use Ask for backend changes when you want the agent to explain the action before it runs.

Stripe connector

The Stripe connector controls whether Stripe-related work is allowed and which payment capabilities the agent may consider.

It can govern capabilities such as:

• Reading account status.
• Managing products and prices.
• Creating checkout sessions.
• Managing subscriptions.
• Issuing refunds.
• Handling disputes.
• Reading payment summaries.
• Managing webhooks.

The connector does not store Stripe keys. Project payment credentials belong in the Builder Payments setup for that project.

When to change connector settings

Change connector settings when:

• A workspace wants stricter governance.
• A project needs to block a sensitive capability.
• A team wants the agent to ask before touching backend or payment operations.
• A payment or backend feature should be disabled for a specific project.

Copyable prompt

Before changing this project, inspect the active connector policies.
List which RIB Cloud and Stripe capabilities are allowed, ask-only, or denied.
If an operation is denied, suggest a safe alternative.

Next steps

• Manage shared settings: Workspace integrations
• Configure app payments: Stripe
• Review backend auth: Authentication