Summary and recommendation
Yotpo 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.
Yotpo's team management lives at Settings > Account > Team Members (https://yap.yotpo.com/#/settings/account).
The permission model is role-based with two confirmed roles Admin and Member
where Admins hold full access to products, billing, and team management, and Members are scoped to features assigned by an Admin.
Granular per-product permissions (across Reviews, SMS, Loyalty, Subscriptions) are not publicly documented, so exact access boundaries for Members are unconfirmed.
Custom roles are not supported.
There is no SCIM provisioning, meaning every app in your identity stack that relies on automated lifecycle management will not sync with Yotpo natively.
Quick facts
| Admin console path | Settings > Account > Team Members |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Unknown |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Full access to all Yotpo products, settings, billing, and team management. | Role definitions and exact permission boundaries are not fully documented in publicly accessible official docs. | |||
| Member | Access to product features assigned by Admin; typically cannot manage billing or team members. | Cannot manage billing, cannot invite or remove other users. | Exact permission scope per product (Reviews, SMS, Loyalty, etc.) is not publicly detailed in official docs. |
Permission model
- Model type: role-based
- Description: Yotpo uses a role-based model with at minimum Admin and Member roles. Granular per-product or custom role configuration is not confirmed in publicly available official documentation.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Coarse role-level access (Admin vs. Member); per-feature granularity not publicly documented.
How to add users
- Log in to the Yotpo dashboard.
- Navigate to Settings > Account > Team Members.
- Click 'Invite Team Member' or equivalent button.
- Enter the invitee's email address and select a role.
- Send the invitation; invitee receives an email to accept and set up access.
Required fields: Email address, Role selection
Watch out for:
- Invitation flow and exact field labels are not fully confirmed from publicly accessible official documentation.
- SSO-based login requires enterprise plan; without SSO, users authenticate via email/password.
- No SCIM provisioning is available, so users cannot be auto-provisioned from an IdP directory.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | No | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Official documentation does not explicitly describe whether removing a team member constitutes a permanent delete or a deactivation. Behavior is unconfirmed from publicly available sources.
- Navigate to Settings > Account > Team Members.
- Locate the team member to remove.
- Select the option to remove or revoke access (exact label unconfirmed from public docs).
| Data impact | Behavior |
|---|---|
| Owned records | Not documented |
| Shared content | Not documented |
| Integrations | Not documented |
| License freed | Not documented |
Watch out for:
- Data impact of removing a user (e.g., effect on reviews, campaigns, or automations they configured) is not documented in publicly available official sources.
- No SCIM deprovisioning means offboarding must be performed manually in the Yotpo dashboard.
License and seat management
Seat type details are not yet verified for this app.
- Where to check usage: Not documented
- How to identify unused seats: Not documented
- Billing notes: Yotpo pricing is product-based (Reviews, SMS & Email, Loyalty, Subscriptions) rather than per-seat. Seat counts and per-user billing details are not publicly documented. Enterprise pricing is custom and negotiated directly with Yotpo.
The cost of manual management
Because Yotpo has no SCIM support, every provisioning and deprovisioning action requires a manual step in the dashboard. For teams managing Yotpo access through Okta or Entra ID, there is no automated sync - joiners, movers, and leavers must each be handled individually.
Yotpo's pricing is product-based rather than per-seat, so unused access does not directly translate to a license cost. However, stale accounts with Admin roles represent a security exposure that only manual audits can surface. There is no documented path to check seat usage or identify inactive users from within the dashboard.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Yotpo's manual user management is workable for small teams but becomes a compliance liability at scale. The two-role model (Admin / Member) is coarse, and per-product permission granularity is undocumented - making it difficult to enforce least-privilege access across Reviews, SMS, or Loyalty modules.
SSO via SAML is available but requires an enterprise plan, and SSO alone does not provision or deprovision users. Teams with strict offboarding SLAs should treat every Yotpo user removal as a two-step process: delete from the dashboard and, if SSO is active, disable in the IdP.
Bottom line
Yotpo's team management covers the basics - invite by email, assign Admin or Member, remove manually - but it is not built for automated identity workflows. There is no SCIM, no granular role configuration, and no documented way to audit inactive users from the dashboard.
For organizations where every app must participate in a governed user lifecycle, Yotpo requires a compensating control: either API-based provisioning or a disciplined manual offboarding checklist tied to your IdP.
Automate Yotpo 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.
