Segmenting by user access and feature permission
If a user's level of permissions is highly customizable in terms of what features they may or may not have access to, what is the best way to capture the permission level to create segments to target guides against and look at the respective data? I want to avoid showing guides to a user that does not have access to a certain feature.
0
Comments
If the user permissions for your product have a high degree of granularity, then it may be appropriate to have that information passed over as boolean metadata. For example: Can_Publish_Reports or Can_Edit_Acct_Detail as boolean flags. You might not need all permissions as metadata, just those pertinent to the segmentation you might require.
Hi Kelly,
To Greg's point, you can utilize metadata to reflect a user's permission to be able to segment from it. If you're not able to pass it through the agent, you can create it as a custom field in Data Mappings and apply it to your internal users. Creating it as a custom field doesn't require any additional dev work.
Please sign in to leave a comment.