Details about this thread
  • State Not Answered
  • Replies 3 replies
  • Subscribers 314 subscribers
  • Views 156 views
  • Users 0 members are here
Related content from around SugarClub

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

Phuong Trinh

Hi everyone,

I'm looking for a way to prevent users from editing the "Account" Field in the Contact module. Ideally, i'd like to achieve this without custom coding.

I'm considering using a BPM Workflow to enforce this restriction. Is BPM the optimal solution for this use case ? If so, could you suggest the best approach to design the BPM process for this requirement ? 

Any insights, alternative solutions, or exemples would be greatly appriated ! :) 

Thanks in advance for your help.

Parents
  • 0

    Hi  

    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.

    Bruce McIntyre

Reply
  • 0

    Hi  

    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.

    Bruce McIntyre

Children
No Data