Restrict Chatter Feeds from User/Profile - Answers - Salesforce Trailblazer Community
Trailblazer Community
Ask Search:
Theo RandTheo Rand 

Restrict Chatter Feeds from User/Profile

  • Use case: Custom object enabled with Feed.
  • Small company -- no Chatter adoption currently, and don't anticipate for mid-term future.
  • User wants to post files to the custom object via FEED but wants the file to private. 
  • Object is child to Accounts -- Master-Detail.
  • All users can see all Accounts.
  • Therefore, all users can see Custom objects.
  • Therefore, all users can see Feed files attached to Custom object.

Objective is to hide the files, but allow the object record to be viewed. 
I think a simple way to do this would be to restrict other users from having access to Chatter. But I don't see a way to do that in Profiles or the User panel. 
Best Answer chosen by Theo Rand
Adam MarksAdam Marks
Sharing is done to extend access, not restrict it so you would want to change your Organizational Wide Default Sharing Settings for the objects in question and then grant access from there.

All Answers

Adam MarksAdam Marks
Chatter is on or off for the company. You would have to restrict access to the record to prevent other users from seeing the feed. Anyone who can view the record could see the feed. Now that being said when a document is attached the user who uploaded it could mark it as private and then use the file sharing options to open it up to other users or groups. It would be manual but is an option.
Theo RandTheo Rand
Thanks, Adam: However, marking the document as private automatically removes it from the record. :( It's the record-attachment that is key here. Can you advise on how I can restrict access to a commonly-available custom object based on the specific records? Is that possible in such a parent-child relationship where all Accounts are visible to all? 
Adam MarksAdam Marks
Sharing is done to extend access, not restrict it so you would want to change your Organizational Wide Default Sharing Settings for the objects in question and then grant access from there.
This was selected as the best answer