Addressing Access Issues for Custom Properties Using PII in Reports

we're removing access to some user/event properties that contain PII, but we use this info in some custom properties that we use quite frequently and that don't expose any PII themselves. the issue is that since these custom properties use PII, dashboards that use them are completely blocked to users without PII access. for example: we have a property that labels the user company, based on their email address. is there a way of exposing reports that use properties based on PII to users without PII access?

2 comments

kapa.ai
APP
·
·
Hi Tiago A., 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
kapa.ai
APP
·
·
Based on the information provided in the knowledge sources, there are a couple of approaches you can consider to address this situation: 1. Data Classification: Mixpanel offers a feature called Data Classification that allows you to mark specific properties as classified. This feature is available for Enterprise plan customers. By using Data Classification, you can control which users or teams can view certain properties, including those derived from PII.You can mark the custom properties that don't directly expose PII (like the company label derived from email addresses) as classified data. Then, you can grant access to these classified properties to specific users or teams who need to see this information in reports and dashboards.Data Views & Classification provides more details on how to implement this: "Marking properties as classified limits which users can view them. Navigate to the event properties and user profile properties tabs in Lexicon to mark a property as classified."2. Data Views: Another option is to use Data Views, which allow you to manage data access for groups of users within a single Mixpanel project. You could create a Data View that includes the custom properties derived from PII but excludes the raw PII data.Data Views & Classification explains: "Data Views enables Project Owners and Admins to manage data access for a group of users within a single Mixpanel project for privacy and productivity purposes."By implementing either of these approaches, you should be able to expose reports and dashboards that use properties derived from PII to users without giving them direct access to the PII itself. However, you'll need to carefully manage these settings to ensure that you're maintaining the appropriate level of data protection and access control.Remember to consult with your legal and compliance teams to ensure that your approach aligns with your company's data handling policies and any applicable regulations.
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.

Addressing Access Issues for Custom Properties Using PII in Reports | Mixpanel Community