Summary and recommendation
Mixpanel 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.
Mixpanel uses a two-tier, role-based permission model: organization-level roles (Owner, Admin, Member) and project-level roles (Owner, Admin, Analyst, Consumer). There are no custom roles - permissions are fixed per role at both tiers. A user's effective access is the combination of their org role and any explicit project-level assignments.
SCIM provisioning is available on the Enterprise plan only, and SSO must be configured before SCIM can be enabled. On Free and Growth plans, every app in your stack that needs automated lifecycle management will require manual user administration in Mixpanel.
Quick facts
| Admin console path | Organization Settings → Users & Teams (org level) or Project Settings → Access (project level) |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Enterprise |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Organization Owner | Full control over the organization: manage billing, delete the org, manage all members and projects, assign any role, configure SSO/SCIM. | Cannot be removed by other admins; only the owner can transfer ownership. | All plans | No per-seat cost; Mixpanel uses event-based pricing. | Only one Owner per organization. Ownership must be explicitly transferred before the current owner can leave. |
| Organization Admin | Manage org-level members, create and delete projects, configure org settings, assign roles up to Admin. | Cannot manage billing or delete the organization. Cannot assign Owner role. | All plans | No per-seat cost. | Org Admins can add themselves to any project within the org, which may be unexpected for project owners. |
| Organization Member | Can be added to individual projects; has no org-level administrative access by default. | Cannot create projects, manage org members, or view org-level settings. | All plans | No per-seat cost. | Being an Org Member does not automatically grant access to any project; project access must be granted separately. |
| Project Owner | Full control within a project: manage project members and their roles, configure project settings, delete the project. | Cannot manage org-level membership or billing. | All plans | No per-seat cost. | Project Owners can be overridden by Org Admins/Owners who can add themselves to any project. |
| Project Admin | Manage project members and roles (up to Admin), configure project settings, access all project data. | Cannot delete the project or assign Project Owner role. | All plans | No per-seat cost. | |
| Project Analyst | View and create reports, dashboards, and saved queries. Can share content within the project. | Cannot manage project members, change project settings, or delete other users' content. | All plans | No per-seat cost. | Default role when inviting new users to a project on most plans. |
| Project Consumer | View-only access to shared dashboards and reports. Cannot create or edit content. | Cannot create reports, edit dashboards, or access raw data views. | All plans | No per-seat cost. | Consumer role is useful for stakeholders who only need to view pre-built dashboards without editing rights. |
Permission model
- Model type: role-based
- Description: Mixpanel uses a two-tier role-based model: organization-level roles (Owner, Admin, Member) and project-level roles (Owner, Admin, Analyst, Consumer). A user's effective access is the combination of their org role and any project-specific role assignments. There are no custom roles; permissions are fixed per role.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Role-level only. Permissions are predefined per role at both org and project scope. No field-level or report-level permission granularity beyond role boundaries.
How to add users
- Log in as an Org Owner or Org Admin.
- Navigate to the Organization Settings page (mixpanel.com/settings/org).
- Click 'Users & Teams' in the left sidebar.
- Click 'Invite Users'.
- Enter the invitee's email address.
- Select the organization-level role (Admin or Member).
- Optionally, select one or more projects to add the user to and assign a project-level role for each.
- Click 'Send Invite'. The invitee receives an email and must accept to gain access.
- For project-only invites: navigate to Project Settings → Access, click 'Add Users', enter email, select role, and save.
Required fields: Email address, Organization role (Admin or Member), Project role (if adding to a project)
Watch out for:
- Invitees must accept the email invitation before they appear as active users; pending invites are shown separately.
- If SSO with IDP Managed Access is enabled on Enterprise, users should be provisioned via the IDP rather than manual invite to avoid sync conflicts.
- Adding a user at the org level does not automatically grant them access to any project; project access must be assigned explicitly.
- Users invited to a project who do not yet have an org-level account will be created as Org Members automatically.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: Mixpanel allows removing (deleting) users from the organization or from individual projects. Removing a user from the org revokes all access across all projects. There is no 'deactivate' state distinct from removal; the user is simply removed. If SCIM/IDP Managed Access is enabled, deprovisioning in the IDP removes the user from Mixpanel automatically.
- Log in as an Org Owner or Org Admin.
- Navigate to Organization Settings → Users & Teams (mixpanel.com/settings/org/users).
- Locate the user in the member list.
- Click the three-dot (⋯) menu next to the user's name.
- Select 'Remove from Organization'.
- Confirm the removal in the dialog. The user loses all org and project access immediately.
- To remove from a single project only: go to Project Settings → Access, find the user, click the three-dot menu, and select 'Remove from Project'.
| Data impact | Behavior |
|---|---|
| Owned records | Reports, dashboards, and saved queries created by the removed user remain in the project and are still accessible to other project members. Ownership is not transferred automatically. |
| Shared content | Shared dashboards and reports created by the removed user continue to exist and remain viewable by users they were shared with. |
| Integrations | API tokens and service accounts associated with the removed user's personal account may stop functioning if they were used for integrations; project tokens are unaffected. |
| License freed | Because Mixpanel uses event-based pricing (not per-seat), removing a user does not reduce the billing amount. No seat license is freed in a monetary sense. |
Watch out for:
- Removing a user does not delete their historical activity or the data they sent to Mixpanel.
- If the user was the sole Project Owner, the project will have no owner until an Org Admin reassigns the role.
- With IDP Managed Access enabled, removing a user in Mixpanel manually may be overridden at next IDP sync if the IDP account is still active; deprovision in the IDP first.
- Personal API tokens created by the removed user will stop working; any automations using those tokens must be updated.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Free Plan | Up to 1M monthly events, 5 saved reports, unlimited users (no seat cap documented), core analytics features. | $0/month |
| Growth Plan | Unlimited saved reports, unlimited users, Modeling Layer, email support. Event-based pricing above 1M free events. | $20/month base + $0.28 per 1,000 events beyond the 1M free tier (approximate; varies by volume) |
| Enterprise Plan | Everything in Growth plus SSO, SCIM provisioning, IDP Managed Access, advanced access controls, dedicated support, data views, group analytics. | Starting $833/month ($10,000/year); actual pricing negotiated based on event volume. Range typically $20,000–$200,000+/year. |
- Where to check usage: Organization Settings → Plan & Billing (mixpanel.com/settings/org/billing) shows current event consumption and plan details.
- How to identify unused seats: Navigate to Organization Settings → Users & Teams to view all org members and their last-seen activity. There is no built-in 'inactive user' report; admins must manually review the user list or use the Mixpanel API to query user activity.
- Billing notes: Mixpanel bills on event volume, not per user seat. Adding or removing users has no direct impact on the monthly bill. Annual prepay discounts of 10–15% are available. Nonprofit and startup discounts of 50–90% off are available through Mixpanel's programs. Enterprise pricing is negotiated annually.
The cost of manual management
Mixpanel bills on event volume, not per user seat, so adding or removing users has no direct impact on the monthly bill. However, the administrative overhead of manual provisioning scales with headcount, not with event volume.
There is no bulk CSV import for users and no domain-based auto-join. Large organizations on Free or Growth plans must invite users one at a time. Identifying inactive users requires manually reviewing the Users & Teams list or querying the API, since there is no built-in inactive-user report.
What IT admins are saying
The most consistent friction point reported by Mixpanel admins is that SCIM is gated behind Enterprise, leaving Growth-plan teams without any automated user lifecycle tooling.
A related complaint is IDP sync drift: users deprovisioned in the IDP can retain active Mixpanel access until an admin manually removes them, if IDP Managed Access is not enabled.
The fixed role set is frequently cited as too coarse. Organizations that need granular, report-level or data-view-level permissions have no path to that without upgrading to Enterprise and using Data Views.
Org Admins silently self-adding to any project is a recurring surprise for project owners who expect project-level isolation.
Common complaints:
- SCIM provisioning is restricted to Enterprise plan only, leaving Growth plan customers without automated user lifecycle management.
- Without IDP Managed Access enabled, Mixpanel and the IDP can fall out of sync-users deprovisioned in the IDP may retain Mixpanel access until manually removed.
- No custom roles available; the fixed role set (Owner, Admin, Analyst, Consumer) is considered too coarse for organizations needing granular permissions.
- No CSV bulk-import for users; large organizations must invite users one at a time or rely on SCIM (Enterprise only).
- No domain-based auto-join or domain whitelisting to automatically add users from a verified domain.
- Org Admins can silently add themselves to any project, which surprises project owners who expect project-level isolation.
- No native inactive-user report; identifying unused accounts requires manual review or API scripting.
- Personal API token invalidation on user removal can silently break integrations if not proactively managed.
The decision
Stay on manual administration if your team is small, your plan is Free or Growth, and user turnover is low. The invite flow is straightforward, and since Mixpanel does not charge per seat, there is no billing penalty for delayed offboarding - only a security exposure.
Move to SCIM if you are on Enterprise, have SSO configured, and need reliable, auditable offboarding. IDP Managed Access is the recommended configuration: it makes the IDP the authoritative source and prevents the sync-drift problem.
Note that project-level role assignments are not fully controlled via SCIM and must be managed separately or via IDP group-to-role mappings.
Bottom line
Mixpanel's manual user management is functional for small teams but does not scale without Enterprise-tier SCIM. The two-tier role model is straightforward to understand but inflexible - every app decision around access control will hit the ceiling of the fixed role set.
The most important operational risk is IDP sync drift on non-Enterprise plans: without automated deprovisioning, offboarded employees can retain access indefinitely unless an admin catches it manually.
Automate Mixpanel 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.
