Recently, we have highlighted new auditing and role-based form functionality in Microsoft Dynamics CRM 2011. Another solid new enhancement in CRM 2011 is field-level security, a feature that controls the ability of users or teams to view or edit a custom field’s contents. Based on their security role in the organization, users can be granted different levels of field security permissions, ranging from Create to Update to Read-Only access. This is a significant improvement from field-level security in CRM 4.0, in which users could access either all or none of the fields on a record out of the box. Fields or tabs could be hidden with custom code, but this method was unsupported.
To demonstrate field-level security, I created a new custom field on the Account form, which I called “Test Field.” The first step is to select “Enable” for Field Security as seen below.
Next, you go to Settings – System – Administration – Field Security Profiles.
Then, you create a new Field Security Profile.
For this example, I labeled the new Field Security Profile as “Test Field.”
After saving the “Test Field” Field Security Profile, you select Field Permissions on the left and the Edit button to edit the Read, Update, and Create permissions. Below, I opted for this security profile to only have Read access of the field labeled “Test Field.”
Next, you select Users on the left and the Add button to add all the appropriate members that you want to belong to and abide by the business rules of this Field Security Profile.
Below, shows how the newly published field appears to users in the Field Security Profile of “Test Field” on the Account form based on our sole selection of the Read-only permission. You will notice the field is grayed out.
A system administrator or other user with all privileges would be able to create, view, and update the field as seen here.
If no permissions were granted in the Field Security Profile, the Test Field would be filled in with a couple of dots as seen below.
Enjoy taking advantage of this field-level security functionality in your organization. Stay tuned for more tips and tricks on using Microsoft Dynamics CRM 2011!
To demonstrate field-level security, I created a new custom field on the Account form, which I called “Test Field.” The first step is to select “Enable” for Field Security as seen below.
Next, you go to Settings – System – Administration – Field Security Profiles.
Then, you create a new Field Security Profile.
For this example, I labeled the new Field Security Profile as “Test Field.”
After saving the “Test Field” Field Security Profile, you select Field Permissions on the left and the Edit button to edit the Read, Update, and Create permissions. Below, I opted for this security profile to only have Read access of the field labeled “Test Field.”
Next, you select Users on the left and the Add button to add all the appropriate members that you want to belong to and abide by the business rules of this Field Security Profile.
Below, shows how the newly published field appears to users in the Field Security Profile of “Test Field” on the Account form based on our sole selection of the Read-only permission. You will notice the field is grayed out.
A system administrator or other user with all privileges would be able to create, view, and update the field as seen here.
If no permissions were granted in the Field Security Profile, the Test Field would be filled in with a couple of dots as seen below.
Enjoy taking advantage of this field-level security functionality in your organization. Stay tuned for more tips and tricks on using Microsoft Dynamics CRM 2011!
No comments:
Post a Comment