Skip to main content

Organization (Global) Connections

Organization (Global) connections are used when your customers' instances reference a third-party account you own. Your customers won't see organization global connections when configuring an instance.

For example, your organization may have a Twilio API key that all of your customers' instances will use for SMS. You want your customers to be able to send SMS messages through your organization's Twilio account, but you don't want each customer to have to enter your Twilio API key when configuring their instance.

Creating a new organization global connection​

To create a new organization global connection, see Managing Connections. When prompted to select the connection type, select My organization's credentials.

FAQ​

What will customer users see?​

Nothing. You as an organization will create the global connection. When a customer configures an instance that relies on that connection, no UI elements will appear in their config wizard.

Can organization (global) connections be used if I have multiple tenants?​

Yes. If your organization has multiple tenants (for example, a US and EU tenant, or a dev and prod tenant), be sure to assign your organization (global) connections the same Stable Key in each tenant. Then, when you sync integrations between tenants, your integrations will automatically use the correct organization (global) connection in the new tenant.