Summary and recommendation
Parse.ly 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.
Parse.ly user management is entirely manual - there is no SCIM provisioning at any plan tier, and all user lifecycle actions (invite, role change, removal) must be performed by an Admin through the dashboard at https://dash.parsely.com. The permission model is a fixed two-role system: Admin (full account control) and Viewer (read-only analytics access).
No custom roles, per-site scoping, or granular permission sets exist.
SSO via SAML 2.0 is available only on the Content Advocacy tier or as a paid add-on, and supports Okta and Entra ID. Critically, SSO does not trigger automatic provisioning - every app user must still be manually invited in the dashboard before they can authenticate via your IdP.
Quick facts
| Admin console path | Dashboard → Settings → Users (or Account Settings → Users) |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Enterprise (for SSO) |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Full access to all dashboard features, analytics data, account settings, and user management. Can invite and remove users, configure integrations, and manage API keys. | Cannot provision users via SCIM; no automated lifecycle management available. | All plans | Included in plan seat count | At least one Admin must remain on the account at all times; you cannot remove the last Admin. |
| Viewer | Read-only access to analytics dashboards and reports. Can view content performance data but cannot modify account settings or manage users. | Cannot invite users, change account settings, access API key management, or configure integrations. | All plans | Included in plan seat count | Seat limits vary by plan tier (e.g., Content Performance: 10 seats, Content Value: 15 seats, Content Advocacy: 20 seats); additional seats may require plan upgrade or add-on purchase. |
Permission model
- Model type: role-based
- Description: Parse.ly uses a simple two-tier role-based model: Admin and Viewer. Admins have full account control; Viewers have read-only access. There are no custom roles or granular permission sets available.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Coarse - two fixed roles only (Admin, Viewer). No per-feature or per-site permission scoping within a role.
How to add users
- Log in to the Parse.ly dashboard at https://dash.parsely.com.
- Navigate to Settings (gear icon) → Users.
- Click 'Invite User' or 'Add User'.
- Enter the new user's email address.
- Select the role: Admin or Viewer.
- Click 'Send Invitation'.
- The invitee receives an email and must accept the invitation to activate their account.
Required fields: Email address, Role (Admin or Viewer)
Watch out for:
- Invitations expire if not accepted; a new invitation must be sent if the link lapses.
- Seat limits are enforced per plan tier; attempting to add users beyond the seat cap requires a plan upgrade or purchasing additional seats.
- SSO-enabled accounts may require users to authenticate via the configured IdP (Okta or Entra ID) rather than email/password after initial setup.
- No bulk CSV import for users is available; each user must be invited individually.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Content Advocacy tier or SSO add-on (Enterprise-level pricing) |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: Parse.ly allows Admins to remove users from the account entirely via the Users settings page. Removal revokes dashboard access immediately. There is no separate 'deactivate' state - removal is the only offboarding action available. No SCIM-based deprovisioning is supported.
- Log in to the Parse.ly dashboard at https://dash.parsely.com.
- Navigate to Settings → Users.
- Locate the user to be removed.
- Click the remove or delete action (trash icon or 'Remove' button) next to the user.
- Confirm the removal when prompted.
- The user's access is revoked immediately.
| Data impact | Behavior |
|---|---|
| Owned records | Parse.ly is a read-only analytics platform; users do not own or create content records within the tool. No data ownership transfer is required. |
| Shared content | Saved reports, dashboards, or custom views created by the removed user may become inaccessible or be deleted; behavior is not explicitly documented for all saved asset types. |
| Integrations | API keys associated with the removed user's account may need to be reviewed and rotated separately by an Admin. |
| License freed | Removing a user frees up a seat against the plan's seat limit, making it available for a new invitation. |
Watch out for:
- You cannot remove the last Admin on an account; a replacement Admin must be assigned first.
- No automated offboarding or SCIM deprovisioning - removal must be performed manually by an Admin.
- If SSO is configured, revoking access in the IdP (Okta/Entra) does not automatically remove the user from Parse.ly; the Admin must also remove them in the Parse.ly dashboard.
- There is no audit log of user removal actions exposed in the standard dashboard UI.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Named User Seat | One invited user (Admin or Viewer) counted against the plan's seat limit. All seats are of the same type regardless of role. | Included in plan; additional seats available as add-on at custom pricing |
- Where to check usage: Settings → Users (shows current user count vs. plan seat limit)
- How to identify unused seats: Admins can review the Users list in Settings to identify users who have not logged in recently; Parse.ly does not surface a 'last login' timestamp in the standard UI per available documentation, so identifying inactive users may require manual review or contacting Parse.ly support.
- Billing notes: Seat limits are set per plan tier: Content Performance (1 site, 10 seats), Content Value (2 sites, 15 seats), Content Advocacy (3 sites, 20 seats). Pricing is custom and pageview-based; average annual cost is approximately $86K, ranging up to $220K. Additional seats or sites require negotiation with Parse.ly sales. No self-serve seat purchasing is available.
The cost of manual management
Every user invite and removal requires an Admin to log into the Parse.ly dashboard individually - there is no bulk CSV import, no API endpoint for user management, and no automated offboarding.
Seat limits are hard-capped per plan tier (10 seats on Content Performance, 15 on Content Value, 20 on Content Advocacy), and exceeding them requires a sales negotiation, not a self-serve upgrade.
Offboarding carries a compounding risk: revoking a user's access in Okta or Entra ID does not remove them from Parse.ly. Admins must perform a second manual removal step in the dashboard, and there is no audit log of removal actions visible in the standard UI.
Identifying inactive seats is also manual - Parse.ly does not surface last-login timestamps in the Users panel.
What IT admins are saying
Practitioners consistently flag the absence of SCIM as the sharpest operational gap, particularly for teams managing access across multiple sites or running frequent onboarding cycles.
The dual offboarding requirement - revoking IdP access and then manually removing the user in Parse.ly - is a recurring source of access-hygiene risk.
SSO being gated to the top tier (or requiring an add-on) is a common friction point for mid-market teams who expect SSO as a baseline enterprise feature.
The lack of last-login visibility in the Users panel makes routine seat audits difficult without contacting Parse.ly support directly.
Common complaints:
- No automated user provisioning (no SCIM support); all user additions and removals must be done manually by an Admin.
- SSO is gated to the Content Advocacy tier or requires an add-on purchase, making it inaccessible on lower-tier plans.
- Revoking IdP access does not automatically remove users from Parse.ly; dual offboarding steps are required.
- No bulk user import via CSV; users must be invited one at a time.
- Limited self-service for enterprise features such as SSO configuration.
- No visible 'last login' or activity data in the Users panel, making it difficult to identify and clean up inactive seats.
- Only two fixed roles available (Admin and Viewer); no granular or custom role configuration.
The decision
Parse.ly is a viable choice for content analytics teams that can absorb manual provisioning overhead and whose headcount is stable enough that seat-cap negotiations are infrequent. The two-role model (Admin / Viewer) is sufficient for most editorial and analytics use cases, but teams needing per-site or per-feature access scoping will find it limiting.
For organizations with active IdP-driven access management, the absence of SCIM and the dual offboarding requirement introduce real compliance exposure. Teams on the Content Performance or Content Value tiers should factor in the cost and process overhead of SSO not being included before committing to a long-term contract.
Bottom line
Parse.ly's user management is functional but entirely manual, with no SCIM support at any tier and a fixed two-role permission model that offers no granularity beyond Admin and Viewer.
Every app user must be invited one at a time, seat limits require sales negotiation to expand, and SSO - available only on the top tier or as an add-on - does not eliminate the need for manual dashboard management.
Teams with high user turnover, strict access-hygiene requirements, or IdP-centric provisioning workflows will carry meaningful operational overhead with Parse.ly in its current state.
Automate Parse.ly 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.
