Restrict 'Profiles' under Customer Management to a specific user group in ACC V8 Web UI

[AnushkaKa1]

Hi Team,

I would like to hide the Profiles folder under Customer Management for a specific user on Adobe Campaign Classic V8 Web User Interface? PFA screenshot for reference.

Could someone guide me with the steps to achieve this?

Thank you in advance.

Kind Regards,

Anushka K

[akshaykapil23]

Hello @AnushkaKa1 

Thanks for posting here. 

To hide the Profiles folder under Customer Management for a specific user in the Adobe Campaign Classic v8 Web UI, you must configure folder-level security settings. Permissions are managed at the operator group level, not for individual operators.

1. In the Campaign Explorer (via the desktop client), navigate to Administration > Access management > Operator groups.
2. Right-click the list and select New.
Enter a descriptive name for the group, such as "Marketing No Profiles".
3.Define the appropriate named rights for this group, making sure not to include any rights that grant broad access to recipient data.
4. Save the new operator group.

Regards

Akshay Kapil

[AnushkaKa1]

Hi @akshaykapil23,

Thank you for your response.

The approach you suggested does help in hiding the PII fields when combined with visibleif conditions, which is much appreciated. However, it doesn’t appear to remove the "Profile" menu under Customer Management in the Web UI.

I’m specifically looking for a way to hide or restrict access to that menu altogether. Appreciate any further suggestions you might have.

Kind Regards,

Anushka K

[ccg1706]

Hi @AnushkaKa1, 

The nearest approach to what you are expecting is to restrict folder access and data visibility through operator group permissions, what will prevent users from viewing or interacting with data within the menu, eventhough the menu still remains vissible. 

My experiences with other projects is that the profiles menu in the UI is part of the default navigation and can't be completely hidden. 

You can take a look to the following documentation: 

-Manage folder permissions 

-Permissions v8 

Best, 

Celia

[AnushkaKa1]

Hi @ccg1706 & @akshaykapil23,

Yes, Adobe Support confirmed that completely hiding the Profiles tab on the Web UI would require customization of the xtk:navTree.

Therefore, I am proceeding with hiding the PII attributes instead of the entire Profiles tab.

I applied the accessibleIf condition to the ctx attribute in the eventHisto schema, as it contains payloads with PII. However, this change seems to have impacted the out-of-the-box mcSync workflow, which syncs data from RT to MKT instance.

Could you please advise if there is a recommended workaround to ensure the workflow continues to run as expected while keeping the ctx field masked? I have tried conditions such as HasNamedRight('admin'), $(loginId) = 0, and $(login) = '', but the workflow still fails to access ctx.

Kind Regards,

Anushka K

@ParthaSarathy 

@Craig_Thonis 

[ccg1706]

Hi @AnushkaKa1, 

I will advise you to ry as a workaround restricting ctx in the schema instead of handling masking at the UI or webApp level. Try to apply the visibleIf condition or use operator group permissions to control who can see the data, without impacting the system. 

Let me know how it works. 

Best, 

Celia

[AnushkaKa1]

Hi @ccg1706,

Thank you for the suggestion.

I’ve applied the accessibleIf conditions at the schema level as advised (which impacted the OOTB mcSync_* workflow). However, I’ve noticed that using visibleIf at the schema level doesn’t actually hide the data on the Web UI.

Please let me know if there's anything else I should try or if there’s a different recommended approach for masking data effectively on the UI without impacting any OOTB workflows.

Kind Regards,
Anushka K

[ccg1706]

Hi @AnushkaKa1, 

Thanks for your update, I don't really know if it will work, but let's try with form and list configurations, combined with operator group permissions  and a name right for the technical operators. This should not impact workflows.

Best, 

Celia

[AnushkaKa1 · Accepted solution]

Hi @ccg1706,

I was finally able to mask "ctx" element within "eventHisto" schema using the below syntax:

<element accessibleIf="HasNamedRight('admin') or $(login) == 'internal' or $(login) == 'admin' or HasNamedRight('customNamedRightName')"

             label="Event XML" name="ctx" type="ANY" xml="true"/>

Kind Regards,

Anushka K