Identity Governance add-on

Manage access to agreement workflows

Give administrators a way to connect enterprise identity systems and manage access to eSignly. Identity Governance supports single sign-on and provisioning controls for eligible accounts.

Available as an add-on subject to eligibility, tier, provider configuration and usage limits.

Connect identity and administration

Select the controls that fit your organization’s identity provider, user lifecycle and access policies.

Single sign-on

Connect supported identity providers using SAML or OIDC so users can authenticate through an enterprise identity system.

Domains and access

Use verified domains and, where available, SSO and session policies to support your organization’s access approach.

User provisioning

Use SCIM, just-in-time provisioning and group-to-role mapping where available to help manage user access and changes.

Identity logs

Use available identity logs to help administrators review access activity.

Availability varies. Connections, provisioning, policies and log capabilities depend on the add-on tier, identity provider and configuration. Confirm your requirements before selecting an option.

Plan your identity rollout

  1. Identify your identity provider, authentication protocol and verified domains.
  2. Map users and groups to appropriate eSignly roles and decide how access changes will be managed.
  3. Discuss your desired provisioning, session policies, logging and expected user volumes with eSignly.
  4. Configure and test access with your administrators before wider rollout.

Frequently asked questions

Is enterprise SSO included in every plan?

Identity Governance is an add-on. Eligibility and available controls depend on your account and selected tier; contact eSignly for details.

What should we prepare for SCIM?

Confirm that your identity provider and selected add-on support the configuration, then plan provisioning, group mapping and testing with your administrators.

Does SSO replace our organization’s access policies?

No. Your organization remains responsible for choosing, configuring and reviewing its access policies and user permissions.