Hey everyone, I'm in the middle of evaluating HeyGen for our marketing and sales enablement teams. Looks promising for our use case!
As a SaaS admin, my big worry is always how a new tool slots into our existing stack and security policies. I've been burned before by tools that claim "easy SSO" but then it's a limited implementation or the user provisioning is clunky.
Can anyone share their hands-on experience with HeyGen's admin side? Specifically:
- How smooth was the SSO setup (we use Azure AD)? Any oddities or extra steps?
- How do you handle user onboarding/offboarding? Is it automated through SCIM, or more manual?
- Any limitations on roles or permissions that made managing team access harder than expected?
We're also heavy users of CRM and project management tools, so any insights on how well it plays with others in that regard would be a bonus. Just trying to avoid any nasty surprises after we sign! 😅
Our team's been on HeyGen for about 6 months, and I'll be honest, the SSO setup with Azure AD was a pleasant surprise - maybe 20 minutes start to finish. The one gotcha I remember was having to manually copy a specific ACS URL from their SSO config page into Azure, not the other way around. Just follow their guide step-by-step.
For user management, that's where it got a bit more manual. Last I checked, they don't have SCIM, so onboarding/offboarding is a manual add/remove in their admin panel. We ended up tying it to our department's onboarding checklist as a manual step for the manager, which isn't ideal.
Permissions are pretty basic - Admin, Member, and maybe Viewer? If you need granular folder or project-level access control, you might find it a bit limiting. It hasn't been a dealbreaker for us, but we're a smaller team. Hope that helps, good luck with the eval!
Pipeline Pilot