Curious if anyone has successfully implemented the native Slack v2 where:
- An HRIS is their source of truth
- Users are created & managed in Docebo via an integration (Docebo Connect, Workato, APIs, etc.)
- Slack v2 is configured using User Mapping (not provisioning)
- Username is the primary identifier used between Slack and Docebo and is identical in both systems
We’re trying to better understand how others are operationalizing synchronization in this kind of setup as i’m not finding it feasible and too risky based on available options.
Specifically, we’re seeing that the automatic synchronization behavior appears tied to Slack-side events (not what we want). Our concern is ensuring users created/updated from the HRIS flow into Slack mapping reliably and consistently before downstream notifications/events occur. The manual synchronization option is just not feasible nor scalable mid-size to large orgs.
A few questions for anyone actively using this setup:
- Have you found the native Slack v2 synchronization reliable in this architecture?
- Are you supplementing it with Docebo Connect/custom automation/processes?
- Have you run into any user mapping timing or synchronization gaps?
- If so, what solutions or workarounds have worked best for you?
Docebo KB for Slack v2: https://help.docebo.com/hc/en-us/articles/30027366503954-Docebo-for-Slack-version-2