How to restrict Editing the "Account" Field in Contact Records without coding

Hi Phuong Trinh , 

Thanks for bringing this up!
In most cases where the requirement is to restrict access or functionality for users, the best approach is to use Sugar's Teams and/or Roles framework.

For your specific scenario, you can restrict editing the "Account" field in the Contact module with the following steps:

1 - Navigate to Admin > Role Management and create a new Role, let's call it  "Account Name - Read Only"

2 - Drill down into Contacts module 

3 - Select the Account Name field and set it to Read-Only 

4 - Add all the users that you want to see this restriction on. 

This should be enough. 
All the users that belong to that role will not be able to Edit the Account field in the Contacts module. 

Let me know if this is what you are looking for. 

Cheers, 

André 

Hello Andre Serrazina , 

Thank you for your suggestion!

To clarify, I would like to restrict users from editing the Account field after the Contact record is created. However, users should still be able to populate this field when creating a new Contact. Once the record is saved, the field should no longer be editable by regular users, but administrators should retain the ability to make changes if needed.

Your suggestion works perfectly for the existing records in our instance, but it doesn’t address the creation of new Contacts. I’m looking for a solution that applies both to existing records and during the creation process for new Contacts.

Let me know if you have any additional ideas or suggestions to achieve this!

Thanks again for your help! 

Hi Phuong Trinh 

To prevent users from editing the "Account" field in the Contact module, BPM workflows may not be the best approach since they are primarily designed for automating processes rather than restricting field access.

Instead, you can achieve this by using Field Level Security or Role-based Access Control:

1. Field Level Security: You can set the "Account" field as read-only or hidden for specific user roles, preventing users from editing it.

2. Role-based Access Control: This allows you to restrict permissions, so only certain roles have the ability to edit the "Account" field, while others are restricted.

Both options are easy to configure and don’t require custom coding.