Skip to main content
All CollectionsSettings
Setting up SSO with trumpet
Setting up SSO with trumpet

Learn how to set up trumpet to work with your SSO provider.

Russell Mitchell avatar
Written by Russell Mitchell
Updated over a year ago

How to Set Up Single Sign-On (SSO) in trumpet

(SSO is available on request or for customers on our enterprise plan - Google is included in all plans)

trumpet supports most SSO providers through our SSO software provider, WorkOS.

We have a long list of providers we integrate with

  • Okta

  • Azure

  • Google

  • SAML

  • Onelogin

  • ADFS

  • Jumpcloud

  • PingFederate

  • OpenID

  • Auth0

  • CyberArk

  • Shibboleth

  • Duo

  • VMWare

  • And many more…

You can find the complete list here: https://workos.com/docs/integrations

With WorkOS, setup takes between 5-15 minutes depending on your identity provider.

If you decide you’d like to opt-in to SSO, contact our customer success team who will setup a call between themselves and the admin of your identity provider. The admin will receive a link to setup SSO for your organisation, they will have to configure your identity provider’s settings.

Once this is done your team will be able to login through SSO to their trumpet account. If they are not invited to trumpet, they will appear in your users & teams page for approval by an admin.

Frequently asked questions

What provisioning technologies do you support?

If a user logs into trumpet using SSO and they have not been separately invited or logged in before. We use JIT provisioning, an admin user within trumpet will have to accept the user before they have access to the account.

If a user has been added via SSO and invited to the trumpet platform, we use directory sync, access can be controlled directly through your IDP provider.

Can we separate SAML and SCIM?

Yes via WorkOS.

What organizational data do you need to know about our users so that the Trumpet platform can succeed?

- In the context of SSO, we receive:

- An email.

- First name

- Last name

- A user ID.

- When you setup SAML you have a prompt which explains how to set this up.

- Additionally, once in the platform, users can manually add their LinkedIn URLs and phone numbers, which if added, are used in certain widgets (if they decide to) to display to an end prospect.

Can trumpet send emails from your domain?

- There are two emails that we can send on behalf of your company.

- One is if the email verification is turned on, this email can be whitelabelled(with the Enterprise plan)

- The other is if someone is tagged in a comment. This can also be whitelabelled(with the Enterprise plan)

- We do not support sending from custom domains as of right now. However, it is something we're actively exploring.

- We do allow custom domains for the microsites themselves (i.e. hub.yourdomain.com could be used). We have a configuration wizard within trumpet that displays the relevant DNS records. You can use any subdomain you wish.

What security features exist?

- We are fully SOC2 Type II and ISO27001:2022 certified.

- We conduct regular vulnerability scanning and pentesting.

- Users are auto-logged out after 24 hours.


Did this answer your question?