@Frank - Excellent question, as component visibility filters are not available in Classic. We only use Lightning (after 2 months of training sessions to move our entire org from Classic to Lightning) we have turned off the ability to switch back to Classic. Since Contracts are aligned with Account security, you "might" be able to create some of the needed security with criteria based sharing rules on the Account object. We created new record types for our Contracts process, this may assist you a little further, BUT, you would still need to look at all of your view, reports and dashboards where Contracts are referenced. Create a sandbox if you havent already, and try it first, good luck :o)
Just a quick reminder to anyone on this thread that is a Lightning User. Our company has multiple groups and affiliates that access the same Salesforce instance, and I've found that using Dynamic Lightning Pages (criteria based filters at the page level) have enabled me to manage my security and visibility issues amongst my users. By using the Department field on the user record, and creating a Component Visibility Filter on my Contract Page (but not the Highlights Panel), my users can only see Contract Details for Contracts created by users in their Department. The beauty here is that they can still see information from the Contract Highlights Panel from other Departments, meaning that they can see that we have 5 Contracts with an Account, but they can only see the details from the 2 Contracts from their department. Additionally, I created a formula field that defaults to a value of YES for Contracts they have access to, and NO for the ones they don't. Doing this enabled me to create a custom Contract View called "My Departments Contracts" for when the value is Yes,
Antti Haanpää - 1 year ago
Considering how sensitive and business critical information can be burried behind contracts, it is somewhat amazing this feature is missing. Definitely needed and not having this available probably leads companies to implement their own Contract model using custom objects, which compromises long term platform integrity, feature carryover and compatibility.
Joseph Desch - 1 year ago
This is especially important when it comes to using Salesforce CPQ. Since CPQ uses the standard contract object, we're subject to these rules for renewal and amendment access. I've seen several scenarios where a company has a renewal team separate from their new sales team, and they need different levels of access on contracts and accounts. Would love to see this put into place, and I'm always surprised it is not already.
Jeremy Bauman - 1 year ago
How has this been open for 10 years and still not addressed? We have multiple cases where we need our OWD for Contracts to be private and opened up via sharing rules where applicable. Not everyone that can see an Account should be able to see the Contracts associated with that Account.
Debra Anderson - 1 year ago
We need sharing on Contracts to be more granular that at the Account level. Similar to opportunity teams we may have multiple sellers on a Contract/Orders.
Wonder how long this has been under product team review? It's hard to tell if this will actually happen anytime soon :-(
Just a follow up to my previous post - it turns out that we had a subset of users that we wanted to have View All access to Contracts, so I created a custom User field, a checkbox entitled View All Contracts.
Now all I need to do is check this checkbox field on our Executive Staff and our System Admins, and we have exactly the access and visibility we need.
**PLEASE NOTE - this works by adding a Filter to the Contract Page in LIGHTNING where the above formula calculates toa value of YES. This functionality will not work in Salesforce Classic.