Integration types

Each application in the Integrations list (Admin > Integrations) has a type. This determines what sort of data will be brought across into Trelica.
Identity integrations provide information about all the users, and the applications they are accessing that the Identity provider is aware of. A good example of an Identity integration is Okta. Okta is often used to configure Single Sign On to multiple other applications. By connecting to Okta, Trelica will add all these applications to Trelica's inventory, as well as information about which users are using these applications.
Usage integrations provide information about specific applications, typically in more detail than can be provided by an Identity provider.
Finance integrations import transaction data from an accountancy tool. This can uncover spend with vendors which can be used to add to (or map to existing) applications in the inventory, as well as importing the associated spend data.
Another form of integration is Single Sign On (SSO). This allows users to connect to Trelica without needing a Trelica-specific password.
If you use Google or Microsoft Azure AD to provide user accounts, then your users can connect to Trelica using a form of SSO called OAuth2. This needs no additional configuration.
Alternatively your organization may use an Identity Provider (IdP) that supports SAML2 for SSO such as Okta, OneLogin or JumpCloud. We have separate configuration instructions if you want to connect an IdP to Trelica using SAML2.