One corporate login for Goodays

Single Sign-On (SSO) lets employees access Goodays with the corporate credentials they already use for company applications. Your Identity Provider (IdP) authenticates the user and Goodays acts as the Service Provider (SP).

For users, this means no additional Goodays password to remember. For your IT team, authentication remains under the control of your existing identity platform and policies.

SAML v2 compatibility

Goodays supports SAML v2, a widely adopted enterprise SSO standard available in identity platforms such as Microsoft Entra ID, Okta and Ping Identity.

Goodays does not support OpenID Connect or OAuth alone as standard SSO protocols. If your identity platform cannot provide SAML v2, contact Goodays before designing the integration: a feasibility request can be submitted to assess an alternative protocol.

Two SSO models

Both models provide the same simple login experience. The difference is how Goodays accounts and access rights are managed.

Static SSO

Choose Static SSO when your main objective is corporate authentication. It is the fastest option to implement: once the SAML metadata has been exchanged, only a few configuration steps are required on the Goodays side. Users are created and managed in Goodays before they authenticate through your IdP.

Read the Static SSO guide

Dynamic SSO

Dynamic SSO still relies on standard SAML v2. It adds account creation and updates by carrying more user data in the SAML response, which Goodays maps to the agreed profile and access rules. It can be relevant for large or frequently changing user populations, provided the identity data is sufficiently structured and stable.

🚧

Dynamic SSO is not a turnkey option

Every Dynamic SSO project requires a preliminary workshop with your business and IT teams. Goodays then reviews the requested provisioning model and confirms whether the integration can proceed. Implementation starts only after explicit Goodays validation.

Read the Dynamic SSO guide

How an SSO project is set up

1. Confirm the target scope

Goodays and your team identify the users, email domains and identity platforms concerned by the rollout. At this stage, we also confirm whether Static SSO or Dynamic SSO matches your needs.

2. Exchange SAML metadata

Goodays provides the Service Provider information required to create the application in your IdP. Your identity team configures the application and returns the IdP metadata so that both systems can establish trust.

3. Configure the selected level

For Static SSO, the relevant user accounts and access rights are prepared in Goodays. For Dynamic SSO, configuration starts only after the workshop, attribute specification and Goodays validation described in the dedicated guide.

4. Validate the login journey

Both teams verify the redirection, authentication and resulting Goodays access with representative users. Dynamic SSO validation also covers the approved account-creation and update rules.

5. Coordinate the rollout

Once the expected journeys have been validated, Goodays and your team agree on the production activation for the intended population.

Project-specific identifiers, URLs, metadata and configuration values are shared directly by Goodays during the implementation.

Have a question?

The dedicated FAQ covers compatibility, user provisioning, organizations with several IdPs and the configuration lifecycle.

Browse the SSO FAQ