Mixpanel Data Governance: Restricting Sensitive User Properties for Lower-Permission Analysts

Pawel A. · 2026-08-28T16:36:03.055Z

@kapa.ai Is there a built-in way in Mixpanel to restrict visibility of specific sensitive user properties (like email or phone) so that certain analysts with lower permission levels cannot view them, while still having access to the rest of the project data? Or is data governance (hiding/masking columns) only available via Enterprise-tier permissions?

Mixpanel Data Governance: Restricting Sensitive User Properties for Lower-Permission Analysts | Mixpanel Community

1 comment

· Sorted by Oldest

kapa.ai
APP
·
(edited)·
Thinking completed
Data governance & access control · 5 sources
Enterprise analytics & governance · 3 sources
Data governance & access control · 3 sources
Done · 11 sources
Yes, Mixpanel has a built-in feature for this called Data Classification, though it does require an Enterprise plan.
Data Classification (Enterprise)
You can mark specific event or user profile properties (e.g., email, phone) as "Classified" in Lexicon. Once marked:
Only users explicitly granted "Can View" access to classified data can see those properties.
Users without that permission cannot use classified properties as filters or breakdowns, and will see a warning if they try to open a report that uses them.
The rest of the project data remains accessible to those users normally.
[Data Classification docs]
As of April 2026, classified data access is managed through a Custom Role permission called "Classified Data Access" (under Data Access, Exports, and Alerts). No default role — including Owner and Admin — has this access by default; it must be explicitly granted. [Roles & Permissions]

Data Views (Growth and above)
Data Views are available on Growth plans and above, but they work differently — they filter events and event property values, not mask individual property columns. They're better suited for restricting access to subsets of data by team, region, or platform, rather than hiding a specific sensitive field. [Data Views docs]
Summary
Need
Feature
Plan Required
Hide specific sensitive properties (e.g., email) from certain users
Data Classification
Enterprise
Restrict access to subsets of events/data
Data Views
Growth+
So yes — granular property-level masking/hiding specifically requires the Enterprise tier via Data Classification. If you're on Growth, Data Views can help with broader data scoping but won't mask individual columns.
⚠️ As a best practice, Mixpanel also recommends not sending PII (like raw email addresses) to your project in the first place. [Privacy guide]
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

kapa.ai
APP
·
(edited)·
Thinking completed
Data governance & access control · 5 sources
Enterprise analytics & governance · 3 sources
Data governance & access control · 3 sources
Done · 11 sources
Yes, Mixpanel has a built-in feature for this called Data Classification, though it does require an Enterprise plan.
Data Classification (Enterprise)
You can mark specific event or user profile properties (e.g., email, phone) as "Classified" in Lexicon. Once marked:
Only users explicitly granted "Can View" access to classified data can see those properties.
Users without that permission cannot use classified properties as filters or breakdowns, and will see a warning if they try to open a report that uses them.
The rest of the project data remains accessible to those users normally.
[Data Classification docs]
As of April 2026, classified data access is managed through a Custom Role permission called "Classified Data Access" (under Data Access, Exports, and Alerts). No default role — including Owner and Admin — has this access by default; it must be explicitly granted. [Roles & Permissions]

Data Views (Growth and above)
Data Views are available on Growth plans and above, but they work differently — they filter events and event property values, not mask individual property columns. They're better suited for restricting access to subsets of data by team, region, or platform, rather than hiding a specific sensitive field. [Data Views docs]
Summary
Need
Feature
Plan Required
Hide specific sensitive properties (e.g., email) from certain users
Data Classification
Enterprise
Restrict access to subsets of events/data
Data Views
Growth+
So yes — granular property-level masking/hiding specifically requires the Enterprise tier via Data Classification. If you're on Growth, Data Views can help with broader data scoping but won't mask individual columns.
⚠️ As a best practice, Mixpanel also recommends not sending PII (like raw email addresses) to your project in the first place. [Privacy guide]
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Need	Feature	Plan Required
Hide specific sensitive properties (e.g., email) from certain users	Data Classification	Enterprise
Restrict access to subsets of events/data	Data Views	Growth+

Need	Feature	Plan Required
Hide specific sensitive properties (e.g., email) from certain users	Data Classification	Enterprise
Restrict access to subsets of events/data	Data Views	Growth+

1 comment

Thinking completed

Data Classification (Enterprise)

Data Views (Growth and above)

Summary

Thinking completed

Data Classification (Enterprise)

Data Views (Growth and above)

Summary