Integration configuration is where you set how a specific relationship syncs: the platform-specific defaults, sync options, and filters for the connection between your organisation and a partner. The available settings depend on the platform, and on whether your organisation is the source or the target.

Use this page once a connection is active and you're ready to control what syncs and how. Field-by-field settings for each platform are in the related articles listed at the end.

Choose the relationship to configure from the Organisation relationship dropdown. The form below then shows the settings for your organisation's platform in that relationship. If you have no relationships yet, you'll be prompted to create one first in Settings.

The exact fields vary by platform, but most configurations group into:

Save your changes with Save configuration, or Cancel to discard them.

Every platform's configuration form ends with an API configuration override section. This works the same way on all platforms, so it's documented here rather than repeated on each platform page.

By default, a relationship uses your organisation-level credentials, the ones entered in Settings. Turn on Override API settings for this relationship to enter relationship-specific credentials instead, so this one relationship connects with a different account or instance. While the override is off, the credential fields are read-only and the organisation-level credentials apply.

Note: Use the override only when a relationship genuinely needs to connect with different credentials from the rest of your account. Most relationships can rely on your organisation-level connection.

The settings on offer depend on your organisation's role in the relationship. Some apply only when your platform is the source (where tickets originate), others only when it's the target (which receives tickets). Each platform page calls out these differences inline.

Detailed settings for each platform: