Summary and recommendation
TinyPulse user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
TinyPulse is an employee engagement and pulse survey platform now operating under WebMD Health Services (formerly Limeade) following a series of acquisitions.
Public-facing admin documentation is not available, which makes pre-purchase evaluation of user management workflows difficult across every app in your environment that depends on accurate headcount.
Teams evaluating TinyPulse should plan to engage the vendor directly to validate any admin capabilities before committing.
Quick facts
| Admin console path | Public TinyPulse documentation does not expose a detailed internal user-admin path; administration appears to happen in the authenticated TinyPulse workspace and gated help content. |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Enterprise |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Manages surveys, settings, and any available user administration inside the TinyPulse tenant. | Detailed public permission boundaries are not documented. | Not publicly documented | Quote-based contract | Public docs do not enumerate a full role matrix. |
| Employee / participant | Participates in engagement surveys and feedback workflows configured in the tenant. | Exact limits versus admins are not publicly documented. | Not publicly documented | Quote-based contract | User onboarding may rely on HRIS or vendor-guided setup rather than a public self-serve workflow. |
Permission model
- Model type: role-based (public details not documented)
- Description: Public TinyPulse documentation does not expose a detailed internal role and permission model, though account administration is clearly separated from participant access.
- Custom roles: No
- Custom roles plan: Not publicly documented
- Granularity: Not publicly documented
How to add users
- Use the authenticated TinyPulse admin workspace to invite or sync users through the tenant-specific people-management workflow.
- Assign any available admin or participant role required in the tenant.
- If SSO or IdP integration is enabled, validate the live tenant flow before relying on automated onboarding.
Required fields: Work email, Tenant-specific role assignment
Watch out for:
- Public help content does not expose the exact invite or sync workflow, so automation should be validated in the live tenant first.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Public TinyPulse documentation does not describe whether users are deleted or deactivated when access is revoked.
- Use the tenant-specific user-management workflow in the TinyPulse workspace to revoke access.
- If an IdP integration is enabled, remove or disable the user in the IdP first so login access stays aligned.
- Confirm historical survey-data impact directly in the tenant because public docs do not describe those semantics.
| Data impact | Behavior |
|---|---|
| Owned records | Not documented |
| Shared content | Not documented |
| Integrations | Not documented |
| License freed | Not documented |
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Quote-based contract | TinyPulse pricing is annual and vendor-quoted rather than publicly documented per-seat tiers. | Custom |
- Where to check usage: Not documented
- How to identify unused seats: Not documented
- Billing notes: Subscription-based, annual contract. Pricing is quote-only via vendor. Known for annual lock-in regardless of actual usage. Contact WebMD Health Services / Limeade sales for current terms.
The cost of manual management
User onboarding and offboarding in TinyPulse relies on the admin UI or CSV bulk import - there is no automated provisioning path confirmed. Without lifecycle automation, IT teams must manually track who has access, reconcile seat usage against an annual contract, and coordinate removals when employees leave.
Annual lock-in means unused seats continue to accrue cost regardless of actual headcount changes.
The decision
If your organization needs documented, auditable user lifecycle management across every app before signing a contract, TinyPulse's lack of public admin documentation is a concrete blocker to evaluate. SSO via SAML 2.0 (Okta, OneLogin) is the documented identity integration path, but automated provisioning and deprovisioning are not confirmed as supported.
Pricing is quote-only through WebMD Health Services / Limeade sales; no public plan tiers are available to reference.
Bottom line
TinyPulse suits teams already embedded in the WebMD Health Services ecosystem who can absorb manual user management overhead and annual contract rigidity.
For organizations that need automated provisioning across every app, auditable offboarding, or flexible seat licensing, the absence of public documentation and confirmed SCIM support makes due diligence difficult without a direct vendor engagement.
Automate TinyPulse workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
