Supported identity providers
If it speaks SAML 2.0, it speaks Donateazy.
Okta
Verified integration. JIT provisioning supported.
Microsoft Entra ID (Azure AD)
Verified integration. Group-based role mapping.
Google Workspace
Verified integration. Org-unit role mapping.
JumpCloud
SAML 2.0 standards-compliant. Works out of the box.
OneLogin
SAML 2.0 standards-compliant. Works out of the box.
Any SAML 2.0 IdP
Upload your IdP metadata XML; we generate the SP metadata back. Done.
Why SSO matters for NGOs
The compliance gain is more than convenience.
Centralised offboarding
When a staffer leaves, disabling them in your IdP revokes Donateazy access in the same second. No more orphan logins in a shared spreadsheet.
MFA inherited from your IdP
Your IT team has already enforced multi-factor auth; Donateazy inherits the same policy. No second MFA setup for users.
Audit logs match your IdP
Every Donateazy session is tied to the IdP-issued NameID. Trace any action back to a named identity across your whole stack.
Role mapping from groups
Map IdP groups to Donateazy roles. "Finance" group → NGO Admin; "Operations" group → Programme Manager. Permissions sync at login.
No password sprawl
Users stop emailing IT for password resets. Helpdesk volume on Donateazy drops to near-zero post-SSO.
DPDPA + audit alignment
Single identity per user is what most data-protection frameworks expect. SSO makes the DPDPA and FCRA audit-trail questions trivial to answer.