As far as I know this should be achievable in the privacy settings within your profile once you change the visibility to yourself, what would leave the username as only information searchable.
Hopefully that is helpful.
Thank you for responding. What I am asking is moreso if Jive has a privacy option set-up similar to Facebook where users can make their profiles fully private. They can navigate the site and are not able to be searched for. Instead, people would only see/interact with them if the private user followed them or initiated the contact.
I unfortunately only know about the function to limit who sees different parts of your profile by editing your privacy settings so will leave this to someone else in case there is more.
1 person found this helpful
Hi Kaleena Narwani,
Reviewing through your description I can confirm that:
What I am asking is moreso if Jive has a privacy option set-up similar to Facebook where users can make their profiles fully private. They can navigate the site and are not able to be searched for. Instead, people would only see/interact with them if the private user followed them or initiated the contact.
This type of feature is not available in the current release. However, if you are interested in seeing this added to a future version, I would recommend submitting an idea to the Ideas for Jive space where our Product team reviews through top rated ideas when considering features for future releases.
1 person found this helpful
It is possible for an admin to make a user "invisible" via the API by changing the visible value to false as shown below.
We don't advertise this though since it is a manual process, but we've done it a few times with users that want to essentially be anonymous and unsearchable within our environment. It also makes it so that their name isn't a hyperlink in posts, etc. We also do this with all of our integration and pseudo accounts (e.g. "Customer Support", "Community Manager", etc.) since we don't want users to be sending those accounts direct messages rather than going through the proper channels.
The one drawback of making this change is that the user's profile will no longer be accessible, even to that user or to admins. Therefore, if for example the user needed to change his/her avatar, an admin would need to change the visible value back to true for them to make the change, and then change the value back. If you try to go to a user's profile (by clicking on "View Profile" as that user or by going directly to the user's profile URL) you will see an error as if the user didn't exist, as shown below.
So this feature can come in handy on occasion, but we use a lot of discretion when utilizing it. When we do need to update the profile, we either use a simple bash or python script to make the change, or we just use a REST client like Postman to run a GET request on the user, copy/paste the JSON into the body of a PUT request and change the visible value, and then transmit and that's all there is to it.
We found that you can actually find their profile in the Admin Console if you know the username.