CRM Accounts Name visibility

Hi,

Need some guidance please; we have multiple sales teams and each salesperson has a view of only their Accounts' records. So they can only see Accounts, Deals, Contacts, Related Modules etc for the Accounts they own.

The technical staff have a view of all Accounts, Deals, Related Modules for both Internal and External Sales accounts but no visibility on cost for Deals and Produces. This was achieved using Sharing Rules.

However, the External Sales team need visibility of a limited set of fields like Account Name, Account Owner and Account Status for ALL Accounts for all sales teams to ensure different teams do not contact the same customer.

Sharing Rules shares the entire Account Module, and we cannot limit field visibility in the Module like we do for the Engineers since the External Sales need to see all the fields for Accounts they own. The limited field view should only apply to Accounts they do not own.

All I can think of is creating a new Module with only the fields that we need to make visible but populating the module would mean an export of the existing Accounts Module, then an import to the new Module and a way to keep it up to date?

Please let me know if this does not make sense.

Any guidance appreciated.

Zoho Desk Resources

Desk Community Learning Series
Digest
Functions
Meetups
Kbase
Resources
Glossary
Desk Marketplace
MVP Corner
Word of the Day

Sticky Posts
Extension pointers for integrating Zoho CRM with Zoho products #8: Upload and manage Zoho Workdrive folders and files from within Zoho CRM
Keeping records on your customers and business prospects is essential for tracking data, conducting follow-ups, and running a business smoothly. When you use two separate applications, and store relevant data in each, checking and tracking data becomes
Extension pointers: Handle cases with personalized solutions using custom actions
In our last post, we detailed the steps involved in creating a custom action and the workflow from the developer and end user's side. Now let's look at a working example of how we can create a custom action and implement it in a Zoho CRM account to make
Extension pointers - Simple yet significant pointers #13: On change of field value for CRM variables
CRM variables provide global access to a variable across an entire extension. They also help in the storage of user-specific data provided by the user at the time of installation, which can later be fetched to perform data functionalities. Additionally,
Extension pointers: Extend end-user benefits and allow personalization by implementing extensions with custom actions
From our earlier post on custom actions, we know that we can create templated actions, share them with end users, and allow them to reuse those actions to achieve personalized outcomes. In this post, we'll look at how custom actions make it easy for users
Extension pointers - Simple yet significant pointers #12: Functions for Zoho CRM extensions
Functions are essential in achieving logical functionality for an extension. You can easily code your functions in Deluge using drag-and-drop tools to meet your requirements. How to create functions for Zoho CRM extensions in Sigma Go to Sigma and select