HRM Interop: Scheduling Provider Webhooks & GDPR Erase

HR updates a provider's role. The booking calendar still shows old availability. Compliance requests erasure. You hunt across HR, CRM, and scheduling.

HRM includes interop built for suite reality — webhooks and GDPR erase with audit — not another HR island.

Guide: HRM buyer's guide

---

Provider-changed webhook → scheduling

When HR updates an employee's provider status (role, active/inactive, bookable):

1. HRM persists change in

   hrm_*

   tables
2. Provider-changed webhook fires to linked scheduling product
3. Scheduling updates availability and assignment rules

No shared DB. Scheduling validates webhook and updates its own schema.

---

GDPR erase workflow

1. Compliance triggers GDPR erase in HRM (authorized role)
2. HRM purges employee PII per policy
3. Audit log records who triggered erase and when
4. Sibling products may require coordinated erase — HRM is the HR system of record

Plan cross-product erasure in discovery; HRM does not silently delete CRM contacts without configured workflows.

---

Employee interop ports

HRM exposes interop port APIs for:

• Migration import from legacy HR stores
• Cross-product employee references (e.g. Projects resource allocation)
• Service link discovery via Suite Platform

---

Configuration checklist

• [ ] HRM SKU entitled on tenant
• [ ] Scheduling service link registered
• [ ] Provider-changed webhook URL and secret configured
• [ ] GDPR erase policy documented with legal
• [ ] Staging test: role change → availability update

---

Honest limits

• External payroll tax filing not in scope
• Recruitment/benefits depth on roadmap
• Coordinated erase across CRM requires explicit integration design

---

Related reading

• HRM lifecycle use cases
• Suite gateway
• Finance use cases

Contact Tekvers · HRM