Loading

Error 'Username does not have access to this record and will not be updated' in Chatter

Publiseringsdato: Aug 21, 2024
Beskrivelse
Publisher Actions can be added to Chatter to allow users to create a record directly from the Chatter feed of another record. When that happens, a post is created in that Chatter feed. 

Users can comment on the post, but may receive an error when attempting to mention someone in that post.

Error:
 
Jane Doe doesn't have access and won't see this update.

If the user continues with the post anyway, the resulting mention will be grayed out and the recipient will not receive an email notification. 
Løsning

This issue occurs if the person being mentioned does not have access to the record that was just created. 

For example:

AW Computing has its Account object set to Public Read/Write, and its Case object set to Private. Jim owns an Account named ACME Testing. Since Sharing Settings are Public, Jane is able to see the ACME Testing account that Jim owns.

From the Chatter feed on ACME Testing, Jim uses the New Case action to create a new case and assigns himself as the owner. When Jim reviews the Chatter feed for ACME Testing, he sees a new post for the new Case that he just created. Jim attempts to mention Jane on the post to let her know that this new case has been created, but he receives an error "Jane Doe doesn't have access and won't see this update." 

Jim decides to save the post anyway but notices that Jane's name is grayed out after it saves. Jane lets him know that she never received an email about the post.

Even though it is in the feed for the Account record that Jane can see, the Chatter comment Jim is making is directly related to the Case that he just created. Since the organization's Sharing Settings are set to Private on Case, and Jim is the owner, Jane cannot see the Case and will not be notified of the mention to her. 

If a Partner or Community user is @mentioned, in addition to having record access, "All with Access" should be selected.

If the object in question is a custom object, the object status should be 'Deployed'.
Knowledge-artikkelnummer

000385948

 
Laster
Salesforce Help | Article