We are finding that when creating a view only role that it is being associated with an Operations or Activity licence. How can we ensure that this role is only attracting a team member licence?
Hi, You can also check out this following blog which mentions that some menu items have an operational level license requirement as the ViewUserLicense parameter, which forces this "read-only" role to require an operational level license. Since the values of the ViewUserLicense/MaintainUserLicense values are set by Microsoft, there is no way to avoid this except excluding these menu items from the role.
Can you tell how the role is being build up? Did you include only standard privileges with read-only permissions? Did you add or change security objects?
A few weeks back, I have also seen another interesting scenario where the read permission was not working, then recreating some custom privileges with only granting read access did solve the issue. I will write a blog about this with mentioning the root cause in the coming weeks.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.