Skip to main content

Hiding some information from the Work category

  • Apr 5, 2023 10:18 AM UTC
  • Sep 17, 2024 10:56 AM UTC
  • 13 replies
  • 485 views
  • Translate All

The work category is visible to everyone by default, it allows one to see an employee's manager and job titles. Changes in the work category are only visible to employees with history permissions, so the employees only see the current data.

However, if you have some fields you would like not to be visible as a part of this category, you can move them to a different category with the needed permissions.

In order to do so navigate to:

  • Settings
  •  Data Management
  •  People’s Data fields  
  • Work category  

Then click on the three dots next to the field you would like to move, you will be able to select a new category for this field.

 

13 replies

Nicole Gibson

The work category is visible to everyone by default, it allows one to see an employee's manager and job titles. Changes in the work category are only visible to employees with history permissions, so the employees only see the current data.

However, if you have some fields you would like not to be visible as a part of this category, you can move them to a different category with the needed permissions.

In order to do so navigate to settings > employee fields > work > by clicking on the three dots next to the field you would like to move you will be able to select a new category for this field.

 

YESSSS!!!!! I second this!  Following incase someone knows the secret. :D 

Right now we have resorted to exporting, creating the field in another section, and importing to update…. not the most ideal option… but one that works - for now. 

It would be great if Bob let us:

  • identify fields or columns that need to be considered “private” or “sensitive” or
  • move them from one table to a field
  • Move a column to another table in the same or different category.
  • Move entire tables from one category to another.

Because of this we have had to make so many categories to restrict access and unfortunately creates a need to duplicate entries or an employee’s profile being super choppy and looooooonnnnnggg.

Translate

Lindsay Sinenberg
Bobber

Hi @Nicole Gibson ! Unfortunately, this is a known limitation. But I will add your company and all of the feedback you provided, to the feature request though!

Translate

Kati Evart

I would also need this feature! :) 

One additional thought for Nicole Gibson’s explanation: duplicating entries is a threat to risk management because when there’s a need to update employees’ data in several fields at the same time, then you have to know, that “somewhere there is something more”. But unfortunately, colleagues and/or admins change, so it growths the possibility of non-compliant data.

Translate

Lindsay Sinenberg
Bobber

@Kati Evart Added! I also added the feedback you provided in your post as well 😊

Translate

  • Jul 17, 2023 12:43 PM UTC

Learn more about Employee fields’ actions. 

Translate

Hi @Lindsay Sinenberg 

Regarding this my question would be who does not need this functionality, as of today the biggest weakness of the product is permission settings and its lack of granularity. Not only for managing profiles, and adequate data access to different departments, but also when using integrations some of them share whole chunks of data that is not needed by the vendor, e.g. personal email address and other PII.

I hope the product team realizes of the importance of this when it comes to GDPR.

Cheers,

Tomas

Translate

I know this thread is old, but came here looking for this answer. We NEED Bob to be able to allow us granularity with turning on/off view access for each field, and not just each category. It’s causing major pain points for us especially around automatic fields that Bob does not let you move to other categories. For example, we need to allow employees to view the entire company’s field of employment type (are they a contractor or regular employee, for example). But we can’t give them permission to the ‘Employment’ category because it also contains FLSA status and pay rate type, which is sensitive data. 

Translate

Adding an additional thought/request to this thread - can Bob separate out permissions needed for a section’s history and future data. E.G. for an individual to be able to view their pay history, they must also have access to view future changes which isn’t ideal in some cases. 

Translate

Olga Frolova

Hi everyone, I double the suggestion from ​@Alpa Patel , we would also ask to separate permissions for viewing previous history and future data. Sometimes we need to hide the future changes until their effective date comes, but also need to show the previous history of the table. 

Translate

Kiare Tavarez
Bobber

Hi ​@Alpa Patel and ​@Olga Frolova! I have gone ahead and added those thoughts as well to the feature request! 😊

Translate

Unfortunately, items within the category table doesn’t have the “Move to Category” option. What’s the alternative method to hide fields in the Category Table?

Translate

Sara Ramos
Bobber
  • Bobber
  • Oct 14, 2025 3:34 PM UTC

Hello ​@Susanna Su 

You’re right, fields inside a category table can’t be moved to another category. As alternatives, you can archive a field to hide it (data stays safely stored), mask its values to limit visibility, or adjust category-level permissions by creating a new category for restricted fields.
Thanks!

Translate

Hi Sara,

Thank you for your reply. Unfortunately, the “Site” is a mandatory field within the Work category table, which cannot be moved or archive. The comp bands are tied to geographic locations/sites, therefore, we are hoping to hide the visibility from everyone.

 

Translate