Skip to content
Help
Get started
Early access: these pages are being written and reviewed. Facts in the header boxes come straight from the product.

Single sign-on

In short. Single sign-on (SSO) lets your team sign in with their work account through your identity provider, such as Okta, Microsoft Entra ID or Google Workspace. Set it up under Settings → Single Sign-On.

Who it is for. The organisation owner or a system administrator, who are the only people who can change single sign-on.

  • Signs people in through your identity provider with SAML 2.0 or OpenID Connect.
  • Routes people to SSO by their email domain: list your domains under Email domains, and the login page sends those addresses to your identity provider.
  • Creates an account on first sign-in for people who do not have one yet, with the role your group mapping or your default role gives them.
  • Can block password sign-in for your domains with Require SSO. System administrators keep password access, so a broken identity provider cannot lock everyone out.
  • For SAML, can also accept sign-ins that start from your identity provider’s app tile, if you turn on Allow IdP-initiated login. It is off by default.
  • It does not handle two-factor authentication itself. Your identity provider asks for the second step; the workspace’s two-factor policy does not apply to SSO sign-ins.
  • It does not import your identity provider’s metadata from a URL. Paste the sign-in URL and certificate by hand.
  • It does not sign in someone who is already signed in as a different person. They have to sign out first (see below).
  1. Open Settings → Single Sign-On and choose SAML 2.0 as the protocol.
  2. Give your identity provider administrator the SP metadata URL and the ACS (Reply) URL shown on the page.
  3. From your identity provider, copy the IdP SSO URL and the IdP X.509 certificate into the form.
  4. Add at least one Email domain, choose a default role, and optionally map identity provider groups to roles.
  5. Turn on Enable SSO and click Save configuration.

Sign-in from the identity provider’s app tile (IdP-initiated)

Section titled “Sign-in from the identity provider’s app tile (IdP-initiated)”

By default, people start SAML sign-in from the Pitch2Sale login page: they enter their work email and click Continue with single sign-on. Sign-ins that start anywhere else are refused.

If your team is used to clicking the Pitch2Sale tile in their identity provider’s app dashboard, turn on Allow IdP-initiated login (sign-in from your identity provider’s app tile) in the SAML section and save.

Leave it off unless you need it. A sign-in that starts at the identity provider cannot be tied to the browser that receives it, so an attacker could trick a signed-out teammate into signing in to the attacker’s own account (a “login CSRF” attack). To limit this, Pitch2Sale refuses an app-tile sign-in when the browser is already signed in as someone else.

Workspaces that already used SAML before this setting existed were switched on for you, so their app tiles kept working. You can turn it off at any time.

  1. Choose OpenID Connect (OIDC) as the protocol.
  2. Register the Redirect URI shown on the page with your identity provider.
  3. Enter the Issuer URL, plus the app ID and secret your identity provider issued, then the email domains and roles as for SAML.
  4. Turn on Enable SSO and save. OIDC sign-in always starts from the Pitch2Sale login page.
  • People sign in from the login page with their work email and Continue with single sign-on.
  • With app-tile sign-in turned on, they can also click the Pitch2Sale tile in their identity provider.
  • If someone sees “You are already signed in as another user. Sign out first”, the browser still holds another person’s session. Sign out of Pitch2Sale, then click the tile again.
Rule Value
Who can change SSO organisation owner or system administrator, from a signed-in session
Email domains at least one before SSO can be enabled
App-tile (IdP-initiated) sign-in SAML only; off by default; refused when the browser is signed in as a different user
Hand-off after an app-tile sign-in single use, expires after about two minutes
Platform switch your Pitch2Sale hosting operator can turn off app-tile sign-in for every workspace; the setting then has no effect
Every sign-in recorded in the audit log, with whether it started at Pitch2Sale or at your identity provider

People get “This sign-in was not started in this browser.” App-tile sign-in is off for your workspace, or was turned off for the whole platform. Start from the Pitch2Sale login page, or turn on Allow IdP-initiated login.

“This sign-in has expired.” The hand-off took longer than about two minutes or the page was reloaded. Click the tile again.