Workspace integrations

Workspace integrations affect more than one project.

Use them for shared governance, account-level setup, and team-wide defaults.

What belongs at workspace level

Workspace-level integration settings can include:

• Connector defaults for RIB Cloud and Stripe.
• GitHub account and RIB GitHub App setup.
• Shared access rules for owners, admins, and members.
• Defaults that new projects inherit.

Project-specific credentials, such as app payment keys, should stay inside the project setup for that app.

Who can manage workspace integrations

Workspace permissions matter:

Role	Typical integration access
Owner	Can manage workspace-level integration settings and ownership-sensitive actions.
Admin	Can manage most shared settings and members, depending on the feature.
Member	Can use available integrations but usually cannot change shared defaults.

If a setting is disabled, locked, or unavailable, check your workspace role before assuming the integration is broken.

Workspace defaults vs project settings

Workspace defaults keep teams consistent.

Project settings handle what one app needs.

Examples:

• A workspace can allow Stripe in general.
• A project still needs its own Stripe keys before checkout can work.
• A workspace can install the RIB GitHub App.
• A project still needs to connect or create its own repository.
• A workspace can allow RIB Cloud auth configuration.
• A generated app still needs real auth screens and routes.

Governance checklist

Before enabling a shared integration:

• Confirm who owns the external account.
• Confirm whether the integration affects all projects or only one.
• Choose Ask for sensitive agent actions if your team is still testing.
• Keep secrets out of prompts, docs, screenshots, and support messages.
• Document who can approve payment, backend, and source-control changes.
• Review project overrides before assuming workspace defaults apply.

Common issues

I can see an integration but cannot edit it

You may be a workspace member. Owners and admins manage most shared settings.

A project does not behave like the workspace default

The project may have an override. Open the project-level integration or connector settings and check whether it inherits workspace defaults.

A payment or auth feature is allowed but still not working

Policy only grants permission. The project may still need credentials, backend readiness, generated app code, or a publish/update step.

Copyable prompt

Review this workspace's integration setup for this project.
Tell me which settings are inherited from the workspace, which are project-specific, and which role is required to change them.

Next steps

• Learn connector policies: Connectors
• Connect source control: GitHub sync
• Review collaboration roles: Project access