A user that is assigned the Marketing Professional - Business role is unable to select a Compliance setting in the Email Settings of the Email Header in a Real time marketing email. The lookup field labeled Compliance is greyed out to the user.
I have tried giving Organization level privileges for Create, Read, Write, Append and Append To on the compliance table, but the user is still unable to set the Compliance setting. The user has Organization level Create, Read, Write, Append and Append to for marketing emails.
The feature switch to allow for Configurable compliance settings is set to on.
Any ideas what it could be?
Yes, exactly the same. Even I as a System User couldn't edit it because I was in the child business unit. However, we can't make our users belong to the parent business user just to edit the field.
We have submitted a ticket to MSFT also. We found that even a System admin in a child business unit was unable to update the field.
Are your users in a child Business Unit, or are they in the root business unit? In our testing we have found that users have to be in the root business unit in order for them to be able to select a setting.
We have the same issue and not only with the Compliance field but the same behavior with the Campaign and Region (own fields) fields on our Marketing Emails. And yes, if you give a higher permission to the user it then they can edit the field. However, that's not a good solution. We don't want to change user's permission set up so they can edit one field. I already submitted a ticket about this to MSFT.
We are having the exact same issue. no changes on our side, yet the compliance field is now blocked for all our users.
We have the same problem and it seems to appeared from 23.5.2023. This has worked for all of our users for one year. No change has been done at security level permission. Now it only works (not greyed out) for the system administrator. For all other users the Compliance field is greyd out. I think this is an error introduced in the Marketing App latly.
Hi Vivian Abalos,
Have you tried giving higher level permissions or checking for field security in the designer?
I think the security role needs to be ruled out first, the second has nothing to do with the setup.
When you see the compliance field appear, the setup has been successful.
If you have more than one compliance field, it is recommended that you only keep the default to try it out; multiple compliance fields can also cause unexpected problems.
André Arnaud de Cal...
291,965
Super User 2025 Season 1
Martin Dráb
230,836
Most Valuable Professional
nmaenpaa
101,156