I have list of user emails whom i want to remove access to overall mixpanel organization account access. can i do i at organisation level or will have to do it at each project. look at latest documentation and community conversation to give accurate think comprehensively. evaluate and share a step by step process. also evaluate which method would be easiest and least time consuming. service account is also an option
Hi Akshay J., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
You can remove access at the organization level (recommended) or at the project level. You do not need to go project‑by‑project unless you specifically only want to remove certain project memberships.
1. Removing user access at the organization level (revokes all projects)
This is the cleanest and least time‑consuming way if you want users to lose access to everything in your Mixpanel org.
Who can do this: Org Owner or Admin (they can “Add/Invite/Remove users to an Organization and or Projects”). [Permissions]
Effect: Deleting a user from the organization:
- Removes them from all projects in that org - Removes them from all teams in that org - Is non‑reversible [Overview]
Steps (per documentation)
For each email you want to remove:
1. Go to Organization Settings → Users & Teams. [Overview] 2. In the Users tab, find the user by email. 3. Check the box next to their name. 4. Click Delete at the top of the table to remove the user from the organization. [Overview]
“Deleting a user from an organization will remove them from all projects and teams within the organization and is non-reversible.” [Overview]
If you have a list of emails, you’ll repeat this per user; the docs do not mention a bulk‑remove UI or API for human users, so this is the most direct documented path.
2. Removing access at the project level only (if you don’t want to remove them from the org)
Use this if you want users to stay in the org (e.g., keep billing access, or be invited later) but lose access to specific projects.
Who can do this: Project Owner or Admin (since they can invite/remove project users). [Project roles; Permissions]
Steps per project
1. Go to the project. 2. Open Project Settings → Project Users. [Overview] 3. Find the user(s), check the box next to their name. 4. Click Delete to remove them from that project. [Overview]
Notes:
- This must be repeated per project they have access to. - If their project access comes via a Team, only an Org Owner/Admin can remove that, and you’d instead: - Either remove them from the team, or - Delete the team to revoke all team‑granted access. [Teams]
3. Service accounts (for scripts/integrations)
Service accounts are separate “non‑human” accounts you might also need to revoke. [Service accounts]
Key points:
- Service accounts are administered by Org Owners/Admins. [Service accounts] - You can: - Delete them at the org level (revokes all project access immediately), or - Remove them from specific projects.
Org‑level deletion (all projects)
From Organization Settings → Service Accounts, deleting a service account “will immediately revoke access to all projects in the organization.” [Service accounts]
There is also an API to remove service accounts from specific projects:
``` http POST /organizations/{organizationId}/service-accounts/remove-from-project Content-Type: application/json
{ "projects": [ { "id": <project_id> , "service_account_ids": [<service_account_id_1> , <service_account_id_2> ] } ] }
LBKSThis removes listed service account IDs from the specified project IDs. [[Service accounts API](https://github.com/mixpanel/docs/blob/main/openapi/src/service-accounts.openapi.yaml)]
---
4. Which method is easiest / least time‑consuming?
If goal = “no access to anything in Mixpanel for these users” → Use org‑level removal:
- One action per user in Organization Settings → Users & Teams. - Automatically handles all projects, teams, Data Views, Classified Data, etc. [Overview; Organizations]
If goal = “remove from some projects but keep them in org” → Use project‑level removal and/or adjust teams, but this is more work (per project and per team).
For automation/integrations → For human users, the docs do not expose a user‑removal API in these sources. For service accounts, you can automate via the Service Accounts API or delete them from org settings. [Service accounts API; Service accounts]
Suggested practical process for your list of emails
1. Confirm your role is Org Owner or Admin. 2. For each email: - Go to Organization Settings → Users & Teams → Users. - Search by email, select, click Delete to remove from the org. 3. Separately, for any service accounts you also want to revoke: - Go to Organization Settings → Service Accounts and delete them there, or - Use the remove-from-project API if you only want to remove them from particular projects.
This org‑level user removal plus org‑ or project‑level service‑account cleanup will be the quickest, least error‑prone way to revoke access broadly.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Let me check the knowledge base for you again. One moment! 📚
Based on the docs you provided, there is no documented bulk API or CSV-based way to remove from an organization by email. All removal flows for users are described only through the UI, one user (or selection) at a time. [Overview]
What is documented:
- To remove a user from an organization, you must: 1. Go to Organization Settings → Users & Teams. 2. Find the user(s). 3. Check the box next to their name. 4. Click Delete. [Overview]
“Deleting a user from an organization will remove them from all projects and teams within the organization and is non-reversible.” [Overview]
- The docs mention bulk invite via CSV, but do not mention bulk delete via CSV or API. [Overview]
- There is an API for service accounts (machine accounts), including a remove-from-project endpoint, but nothing equivalent is documented for deleting human users by email or ID. [Service accounts API]
Given this:
- To remove 200 individual user accounts at the organization level, the only documented approach is to: - Use the Users & Teams UI, filter/search by email in small batches, - Select multiple rows at once, - Click Delete. - You can speed this up by: - Preparing your 200 emails in a list, - Searching for each email (or small sets, if your UI filter supports it), - Deleting in batches via the checkbox selection.
Because the knowledge sources do not describe:
- Any SCIM-based “delete user from org” pattern for you to call directly, or - Any REST endpoint for bulk user deletion by email,
I cannot confidently recommend a programmatic, email-based bulk removal approach beyond what’s documented above. If you need true automation, the only clearly supported automation in these sources is for service accounts, not human users.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.