Works with what you run
Sign-in through the identity provider you already use, and data in and out through a documented API.
Workday
via the partner API
ServiceNow
via the partner API
Corporate Giving HubYour webhook endpoint
Jira
via a webhook workflow
Microsoft Teams
via a webhook workflow
Slack
via a webhook workflow
- Single sign-on
- SAML per organization with Microsoft Entra, Okta, Google Workspace or any SAML 2.0 provider, routed by email domain.
- Everyone else
- Google, Microsoft or Apple sign-in, or a one-time code by email or text, with no passwords to manage.
- Your roster
- Invite by work-email domain, by code or in bulk; a CSV from your HRIS sets departments, titles, regions and cost centers.
- Partner API and webhooks
- Push volunteer hours, read opportunities, check charities and receive signed webhooks, with keys per organization.
Another system can file hours here.
Retry with your own reference and get the first record’s id back, not a duplicate.
We run no native HR connectors today; HR data comes in through the partner API or a CSV import.
Ask for the partner API documentPOST /v1/volunteer-hours
Authorization: Bearer <org key>
{ "email": "dalia.costa@northwind.example",
"occurredAt": "2026-10-08",
"minutes": 180,
"activity": "Food bank sorting shift",
"externalRef": "wd-88213" }201 { "id": "ohs_7yq4m2kd9txb3hn8pc5wr6ef" }the same request again
200 { "id": "ohs_7yq4m2kd9txb3hn8pc5wr6ef" }
Your sign-in and data, connected
Thirty minutes in the real product, with the report first.