Why Hiding Search Bar/ Timeline/Side bar shifted to User DocType from Role Doctype

Earlier we can manage Search Bar/ Timeline/Sidebar from role doctype .Now in latest update it is shifted to user doctype.

How can we hide these for particular role? Doing for individual user is very time consuming and not efficient?

This was done as it didn’t work well with role - you would have to revoke it from desk user role, and create custom roles for users who would have access, since we used to check all assigned roles of a user before deciding the final values for these fields.

Thanks for responding.
But I didn’t get what are you saying:(

I have already custom roles and assigned to the users who are restricted to “Search Bar/ Timeline/Sidebar”. But now that is not working because these validation are shifted to user.

Now I have to do individually or bulk edit with some filters:(

@akhilnarang,

Its better to have it both ways, in role as well as at user level - with the checkboxes in the user taking precendence. This way, we have we have better control over it. We can set it in bulk for multiple users with just a role in one shot, and keep exceptions by adding it for specific users.

In my case, I have 15000 employees. Now, if I would like to hide it for half of my staff, I have to download the user list, segregate the required users, mark the columns and then import the sheet. Whereas, earlier I just need to mark it in the role and voila, it is applied to the required staff.

If the Frappe team added this for specific users, it should also be available for roles. User-specific settings should come first, but if we set it for roles, it should apply to all users in that role unless a user-specific setting is set.

@akhilnarang

The issue is there’s no “disabled” state, only on or off, so its hard to figure out when the user-specific setting should override. Having a select field could fix that perhaps.

When you updated the site, the data from the roles would’ve been migrated to the user (based on the final settings that should apply to the user, after evaluating all their roles - if enabled for even one of their roles, it would be enabled for the user)

@akhilnarang
I agree with @nasir solution

I completely agree with the points raised in this thread. The shift of Search Bar/Timeline/Sidebar visibility settings from the Role Doctype to the User Doctype has introduced significant challenges.

In my company, all the Frappe developers are frustrated with this change because it feels like the update was designed with smaller organizations (e.g., 50 users) in mind. However, in our case, we are dealing with organizations that have nearly 6,000 users. Manually updating settings for every user is not only inefficient but also highly impractical.

Having this functionality available at both the Role and User Doctype levels would make a huge difference. Role-based settings could serve as the default for larger groups, with user-specific settings reserved for exceptions. This would provide a scalable solution without sacrificing flexibility.

I strongly request the frappe team to reconsider and reintroduce role-level functionality. The current approach is causing major inefficiencies for organizations with large user bases, and this change would help address these concerns effectively.