Configuring integrations just got a major upgrade.

Until now, each integration could only have a single configuration - one auth method, one setup. That limited how teams could handle multiple environments, clients, or authentication styles. The new Integration Configs page changes that.

You can now create and manage multiple configurations per integration, each with its own authentication and permission scopes. That means more flexibility for complex enterprise use cases — and tighter control over what’s allowed.

What’s new

• Integration Configs page in the dashboard - lists every integration that can be configured
• Multiple configs per integration - set up different auth methods for the same provider
• Default config selection - define which config is used when none is specified

Why it matters

Teams can now:

• Use different authentication methods for the same integration
• Lock down integrations to specific allowed actions
• Avoid overexposure of access scopes

Learn more about how to set it up in our docs.