0

In our Salesforce instance we need to assign a customer success rep once an account becomes a 'customer'.

We have a picklist for 'type', which has different stages such as suspect, prospect, customer, etc.

I'd like to make it so once the "type=customer", our customer success manager will then have ability to read/write on the account. They will then be able to add an account team and assign the appropriate rep to manage.

As a workaround I can make it so the manager can read/write ALL accounts, but would prefer it only be the customer accounts.

I was trying to accomplish this through using validation rules (IF type=customer, then yada yada) but had problems because 'type' is a picklist value.

Any recommendations? Thank you!

1
  • 1
    Have you thought about criteria based sharing rules for this object? Means you would turn the OWD to Private, with possible additional changes to allow current users override the OWD by Profile but only opening it to your Customers Success Rep when type=customer through sharing rule.
    – TSmith
    May 11 at 19:53
0

Depending on what you want to do, you could use either a validation rule, sharing rules, or roles (if you auto-assign the account to have the CSM as the owner).

Roles and sharing rules are two kinds of record-level access control that Salesforce provides. Profiles and permission sets grant access to particular kinds of things (access to accounts in general, access to particular fields on an account, etc.) Roles and sharing rules allow you to determine access on the basis of record-level criteria.

As TSmith commented, a sharing rule is probably what you're looking for. They allow you to prevent read access (CSM can't see the record in Salesforce) or prevent edit access (CSM can't edit the record).

A validation rule would also allow you to prevent edit access, but the user experience is less desirable, since the user doesn't get blocked until after making edits to the record and saving. Sharing control prevents them from even trying. A validation rule would be appropriate if you wanted to allow the CSM to edit some fields on account, but not all. Picklists can be used in formulas; they just require a special syntax:

ISPICKVAL(Type, "Customer")

The down-side with sharing rules is that you'll need to change account access to private, then extend it out based on criteria or roles. Your users may lose access to things they could previously see, and should see, until any kinks are worked out of your sharing rules.

https://trailhead.salesforce.com/content/learn/modules/data_security/data_security_sharing_rules

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.