All Ideas

Idea Details

Post an Idea

This idea has been delivered and can no longer be voted or commented on. If you’d like to add to this conversation, please post a new idea.

9,010 Points voting closed

Delivered in Winter 15

Subscriber hg001

Restrict Visibility of Chatter by Profile

Chatter & Files

Please allow Chatter visibility to be controlled by the System Administrator. We have certain users that we need to block from using Chatter. Currently, visibility of the Chatter app, as it appears in the drop down menu in the top right hand corder, can be controlled by Setup>Create>App. However, the Chatter features still appear on the home page of every user even if visibility is turned off at the profile level. We need user-level control. Thanks Salesforce! Keep the great developments coming!

· Flag

Latest Comment from Salesforce

IdeaExchange Moderator - 6 years ago

Our Winter '15 release introduces a new profile permission that can enable/disable Chatter for user profiles and give customers the control over who can use Chatter and who can not.

See below for more information:
http://help.salesforce.com/apex/HTViewHelpDoc?id=collab_pbr.htm#collab_pbr&language=en

Flag

Comments ( 128 )

Sort By

IdeaExchange Moderator - 6 years ago

Flag

Phyllis Ly - 6 years ago

I'm glad to see there are more companies that are requesting better control over Chatter users & visibility. We are wanting to roll out Chatter to our Communities users. The challenge is our Communities users may be competitors of one another and thus we do not want them to be able to search for other users or view all chatter feed from all users. It would be nice to restrict the users to groups they have access to, similiar to the sharing rules in place for Accounts and Opportunities.

It looks like they will be making some adjustments to Chatter in the next release (as I was told by a SFDC support rep) so I'm very interested to see what's coming.

Flag

Nick Sakaleros - 6 years ago

We also have certain users that we need to block from using Chatter. Definately need to be able to turn chatter on/off by profile.
- Flag

Alexander Brasaola Aranzana - 6 years ago

Please include the below options for the internal users as well so that, if we want to restrict our internal user from viewing the chatter post we can do it.

Portal User Visibility
Standard Report Visibilty
Community User Visibility

Thanks.

Flag

Shanker Nemani - 6 years ago

So, any updates on this Idea?
- Flag

Ben Gottesman - 6 years ago

Spring 14 introduces Chatter Profile-Based Rollout, but it's only in pilot. Also, it appears that

http://docs.releasenotes.salesforce.com/en-us/spring14/release-notes/rn_chatter_pbr_pilot.htm

Also, they say that the pilot is only for people who haven't rolled out Chatter yet. Hopefully that's only a condition of the pilot and not the feature.

Chatter Profile-Based Rollout—Pilot

Roll out Chatter for a subset of users instead of all users in your organization.

Up to now, enabling Chatter meant giving all users in your organization full access to Chatter. Starting with this release, Salesforceintroduces Chatter profile-based rollout. Use this new feature to make Chatter available for a part of your organization, but not for all users. Once Chatter profile-based rollout is enabled for your organization, your administrator can turn on Chatter for only the users that have been assigned the required user profile or permission sets. All other users in your organization won’t have access to Chatter.

With Chatter profile-based rollout, larger organizations can plan a controlled rollout and deploy Chatter in a way that enhances adoption and engagement on a team-by-team basis. Organizations with regulatory constraints have the option to give full or no access toChatter based on employee roles and profiles.

For example, if you assign a user profile or permission set that excludes Chatter access to a subset of users, these users still have access to Salesforce objects, like accounts, leads, opportunities and so on, but they don’t see the record feed and they can’t make posts.

Chatter profile-based rollout is available through a pilot program. The pilot program is open for customers who currently don’t haveChatter enabled in their organization. For more information about Chatter profile-based rollout, contact your Salesforce representative.

Flag

Michael Mills - 7 years ago

This solution may help some but not everybodies issues.
In order to limit the visibility of community users from seeing other users outside of their scope follow these steps:

1: Under Setup > Security Controls
2: Sharing Settings
3: Edit organization wide defaults
4: under user visibility settings
5: Select or Deselect the user visibilites box.
Portal User Visibility
Standard Report Visibilty
Community User Visibility

Flag

Bergin Panimayam - 7 years ago

I can't agree more with Erik Mittmeyer, we are in the same situation as well. So please allow chatter to be hidden by profile etc.
- Flag
Stuart Werner - 7 years ago

We have users that must comply with FINRA rules. At this time we can't give them Salesforce accounts. They need to have Chatter blocked.
- Flag
Stefanie Causey - 7 years ago

At least need the ability to assign a read only permission within a group!
- Flag
Hervé JOLY - 7 years ago

Really Useful for users which need to use it and another kind of users which don't need it.
- Flag

Jean De Ridder - 7 years ago

We have some licenses for external partners who don't belong to our company. If we don't look out, they can see a lot of private things about our company through the chatter. We should be able to disable chatter on this profile. I think that for a lot of customers it would already be enough to have the possibility to turn off the chatter on 1 profile. Please do it !

Flag

Steven Marquis - 7 years ago

+1
- Flag
Steve Szakelyhidi - 7 years ago

I agree. We need this functionality as an interum step while we qualify the user. So it would be nice to have Chatter restricted just for the onset.
- Flag

Kristen Leffingwell - 7 years ago

We have a need to restrict Chatter availability for people that are self-registering on our Customer Community org. We want to have control over what these users see until we have a chance to "approve" the registration.