Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We have a read-only security role which is linked to a Team. If a case is assigned to that team and a user is also a member of that team, they can edit the record, even though the only security role attached to that team/user is read-only.
Am I missing something here? We have dashboards and views associated to the teams which users must be able to see but only some users should be able to edit the records and these are provided with an additional security role.
You can check following points:
1.You can first check team and users that added to this team has only one security role or not?
2.check the security role is set correct or not?or you can create a new security role that only can read.
3.link the security role to the user not team to test, it is possible not suitable for team.
4.clear cache or change another browser or use privacy mode to test it again.
Please mark as verified if the answer is helpful. Welcome to join hot discussions in Dynamics 365 Forums.
Could you please send screenshot of Security role assigned to the Team. Specfically Case entity permission screenshot to check this issue further.
As suggested in above post you shold also check If User who is also part of that team has any role assigned which is causing this issue.
Thank you for your reply. I linked the security role direct to the user and still had the same issue. I then realised that the user was linked to a generic (access) security role, which should not provide any write permissions but this was set to User Write.
Business Applications communities