Skip to main content

#Record Visibility0 personne en discute

I have 100+ teams and a custom object.

I need to configure security so that for example only members of team A can see records from other members of the same team.

 

Do I need to create 100+ sharing rules manually, is there a more direct way or another workaround?

 

Thanks

 

#Security  #Salesforce Platform  #Record Visibility

2 réponses
  1. 22 févr. 2022, 23:26

    There are many ways that you could implement this

    One of the options is to create queues in the system for each team and add team members to the respective queue. 

    Use Automation to Make the Queue, record owner, and all queue members from the respective team would be able to access the records that the queue owns.

     

    The good thing is There's no limit to the number of queues you can create, and you can choose when queue members receive email notifications.

     

    The other way is to use Apex-based sharing. You would want to maintain the list of teams in the system in a custom object myObj_Team__c and use Apex to create a share the records with all the members that are part of a team.

     

    Please mark this answer as Best Answer if this resolves your issue.

    Also, Let me know in case you need more clarification.

0/9000

The reasoning behind this would be to use a visibility filter on the Potential Duplicate box to hide it if the duplicates are zero. Having the box there permanently makes it less relevant to reps so they ignore it most of the time.

 

#Record Visibility  #Page Layout  #Lightning Record Page

3 réponses
  1. 7 oct. 2021, 04:40

    Hi,

     

    Why don't you crete a report on duplicates:

    https://help.salesforce.com/s/articleView?id=sf.duplicate_management_custom_report_types.htm&type=5

    and group it by Duplicate Report set name. I usually also group it by Name (ie for Contact, Fll Name)

    You can add a chart to it and save it in a shared folder

    This means your duplicate rule needs to be set to "Allow" and Report needs to be checked for creation and update.

     

    You can now add a report chart element to the object lightning page and filter by Contact ID.

    You can now clearly see if there is a graph or not on the page. Unfortunately, you cannot use the visibility functionality here unless you recreate the roll up functionality with flows to see if there are Duplicate Record Items assoicated to the record and update a field with the number of Duplicate Record Items records. You can then state that Number field has to be greater than 0

0/9000

Hi all,

we have the following issue:

CRUD access for Accounts is set to Modify All for the profile ABC. 

CRUD access for Cases is set to Create, Read and Edit for the same profile. Users with this profile are not allowed to delete Cases.

I created a role hierarchy, which looks like this:

 

Sharing Rules with a specific role are not working and still appying Private OWD

The Sharing Rules on Cases look like this:

 

Case Sharing Rules.png

with Read/Write access to cases.

 

The idea is to give users with the profile ABC and role ABC Role access to ALL cases, no matter who created them. If it wasn't for the CRUD access to Cases (No Deletion is possible) I would give users in this profile Modify All access and the solution would be simple.

 

There are Case records created by any users, but if I log in into Salesforce as a user with the profile ABC and Role ABC Role I am unable to see Case records of other users (for example records created by someone in the A or B role). I can see only Case records I created.

OWD for Account and Case is both Private.

 

I am spending hours and hours trying to figure out what could be the cause of this issue.

 

I would appreciate some guidance :).

 

#Record Visibility  #Security  #Sales Cloud  #Service Cloud

20 réponses
  1. 23 août 2021, 16:27
    I think if roles A & B are under role ABC in the role hierarchy, that would solve the problem
0/9000

Hi all,

I am almost new regarding Sharing / Visibility of records and trying with testing some configuration.

 

We have users working as agents in companies associated to ours.

These companies have been created as Accounts of type 'Associated Company' (record type). One is A and the another B. 

Now some users work at A and some at B.

The idea is to allow users at A to see only opportunities related to their Account A. On the other hand, users in Account B should only see opportunities related to the Account B.

 

I am not sure if I am going in the right direction, I created two roles, one as A Agent and the another as B Agent under the CEO. By testing and using an example user for Account A, this user can see all Opportunities, even the ones at B.

 

Our OWD is Public Read/Write.

 

I am very confused and don't know how can I move further as the OWD is Public Read / Write.

 

I would appreciate any guidance.

 

#Record Visibility  #Sharing Settings  #Security  #Sales Cloud  #Service Cloud  #Automation

9 réponses
  1. 13 août 2021, 18:04

    Hi Laura,

    From the situation which you explained seems like you want to share records created by a user working at Company A with all the users working for Company A and same for Company B right!!! 

     

    In that case what you can do is change the OWD Of Account and Opportunity  as Private!!

    So what will happen is only user who created can see the record!! now go to bottom of sharing settings and create a sharing rule on Account and Opportunity, to share the records owned by user working at company A with all the users under role A agent, do same for B!!

     

    To know more on how to use Sharing rule you can check below link and video:

    https://www.sfdcpanther.com/sharing-rules-in-salesforce/

     

    Thus, all the user will get access to opportunity created by user working for Company A only and same for B!

     

    Hope it helps :D

    Let me know if stuck somewhere!

0/9000

Hi all,

Unfortunately I could not find the exact meaning of the option 'Roles, Internal and Portal Subordinates'.

When you have  Partner Community licenses you can create Parter Portal users and for them once the Partner Portal user is cerated the corresponding Portal Role is created automatically.

You have then following options for Sharing Settimg:

  • Portal Roles
  • Portal Roles and Subordinates
  • Public Groups
  • Queues
  • Roles
  • Roles and Internal Subordinates
  • Roles, Internal and Portal Subordinates

Probably the last one includes Roles (Internal and Portal Roles), Internal and Portal Role Subordinates.

Can someone confirm me this?

 

#Record Visibility  #Sales Cloud  #Service Cloud  #Automation

1 réponse
  1. Forum Ambassador Michael Brown (Salesforce)
    14 août 2021, 21:22

    Hey Laura, 

     

    That last option means it will share it with users in the role you've selected, as well as any user in a role that is a descendent of that role, and you can apply this sharing either for internal users or external users in a community. 

     

    For example let's say I have the following role hierarchy:

    • Executive
      • Sales Manager A
        • Sales Rep A
      • Sales Manager B
        • Sales Rep B
      • Sales Manager C
        • Sales Rep

    If I creating a sharing rule and select Roles, Internal and Portal Subordinates and then select the Executive Role, this would share it with users in the Executive Role, as well as users in every other role since those are a descendant of the Executive role. 

     

    Thanks,

    Mikey

0/9000

I want everyone in the org to be able to view only their cases and not the cases of others. Below are the settings I have made. In spite of these settings the managers in the role hierarchy are able to view their subordinates records. How do I restrict it from happening. Every one in the org should only see the cases they own.???? How to achieve this?  Is it because in the OWD we cannot remove the grant access using hierarchies is selected? that the managers view their subordinates cases?

 

Set the OWD as private

The OWD is set to private for the cases, but the grant access using hierarchies cannot be edited, since its an custom object

Profile setting

Untitled1.png

Role setting - no access, only access to the records they own.

Untitled2.png

#Record Visibility  #Service Cloud

3 réponses
0/9000

If a customer requires Role Hierarchy for Record visibility (sharing rules), is upgrading to Professional Edition the only option?

3 commentaires
  1. 3 nov. 2020, 03:44
    Hi @Paul Wnek

    Thank you for posting in the Essentials Community!

    We appreciate your feedback and I have passed it on to our Product Team. Please feel free to share any other product feedback that you have; our customers help us to create the best products possible.

0/9000