Grant of License
Specify permitted use, license scope, sublicensing rights, and whether the license is exclusive, nonexclusive, perpetual, or term-limited; tie scope to user counts or environments.
A clear Software SSO License Agreement reduces integration ambiguity, limits operational and security risks, and preserves contractual remedies if authentication or data access fails. It defines technical interfaces, service levels, and compliance responsibilities so both licensor and licensee can implement SSO without disputes or unexpected liabilities.
Organizations that routinely use or provide identity services prepare this agreement before integrating SSO into production environments.
Legal, security, and product stakeholders should review terms jointly to ensure alignment on technical controls, data handling, and liability allocation.
Typically signs for technical acceptance and integration commitments. Responsible for technical SLAs, authentication standards, and coordinating IdP configuration during onboarding; may delegate execution authority to senior IT management.
Reviews legal terms, liability caps, indemnities, and data processing clauses. Ensures the agreement aligns with corporate policies, compliance obligations, and any required consumer disclosures under ESIGN or state privacy laws.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day trial | Varies | Varies | Varies | Varies |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Specify permitted use, license scope, sublicensing rights, and whether the license is exclusive, nonexclusive, perpetual, or term-limited; tie scope to user counts or environments.
Define supported protocols (SAML, OIDC), endpoints, attribute mappings, SCIM provisioning behavior, and acceptance testing criteria for production rollout.
Allocate responsibility for identity proofing, MFA, session handling, and revoked credentials; state which party manages IdP configuration and user lifecycle.
Document license fees, invoicing frequency, overage rates for additional users, payment terms, and consequences for late payment or disputed charges.
Include security obligations, breach notification timelines, encryption requirements, and compliance with HIPAA, PCI, or applicable privacy statutes.
State term length, renewal mechanics, termination for convenience or cause, transition assistance, and post-termination data disposition.
The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers.
Tech Data uses airSlate SignNow to improve our internal and external customer service while increasing our speed to revenue.
| Field | Configuration |
|---|---|
| SSO Provider | Specify IdP name and endpoints for SAML/OIDC |
| Authentication Method | Choose email OTP, SMS, or SAML assertion |
| User Provisioning | Enable SCIM or manual provisioning flags |
| Audit Trail | Capture IP, timestamp, and signer authentication |
Verify platform support for required integrations, document formats, and authentication modes before finalizing the agreement.
Choose a platform that supports required APIs, has audit trails, offers BAA where needed, and can export signed records in industry-standard formats for long-term retention.
Agreement takes effect on the signed Effective Date.
Allow 30 calendar days for initial IdP/SP configuration and testing.
Require 60–90 days written notice for nonrenewal or amendment.
Typically 30 days' notice for convenience, longer for breaches.
Invoices due within 30 days unless otherwise agreed.