granular controle for Filters in Kibana

[erwin-willemsen]

For some users I would like to be able to disable the search bar and the Add filter (and change filter) at the top of the Kibana screen.
Add granular control for Filters with sub-feature privileges #60563

The use case:
For our company we use Elastic/Kibana for our customers. Some users, being part of a customer, may filter time, but may not use the Search bar or the filter options (Add filter, change filter, Change all filters) in Kibana. They may only see the visualisations and dashboards which are provided to them, including the filters.

[elasticmachine]

Pinging @elastic/kibana-security (Team:Security)

[legrego]

Hey @erwin-willemsen, thanks for opening this enhancement request. This sounds similar in nature to #16898, although that one does not describe this as a security feature.

For your particular use-case, is the current system of sub-feature privileges granular enough, or would you need to make this decision on a dashboard-by-dashboard (or visualization-by-visualization) basis?

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[erwin-willemsen]

Dear Larry, Thanks for your email. The current system of sub-feature privileges will do just fine for me for this use case. However I can imagine that in some cases the decision should be on dashboard or visualization basis. It is a valid question. For me the solution within role-privileges would suffice. Kind regards/Met vriendelijke groet, Erwin Willemsen consultant <mailto:roos.groen@enable-u.nl>+31 (0) 6 11 85 53 50 [http://images.enable-u.com/images/logo%20Enable%20U.png] From: Larry Gregory <notifications@github.com> Sent: dinsdag 28 juli 2020 13:43 To: elastic/kibana <kibana@noreply.github.com> Cc: Erwin Willemsen <erwin.willemsen@enable-u.com>; Mention <mention@noreply.github.com> Subject: Re: [elastic/kibana] granular controle for Filters in Kibana (#73192) Hey @erwin-willemsen<https://github.com/erwin-willemsen>, thanks for opening this enhancement request. This sounds similar in nature to #16898<#16898>, although that one does not describe this as a security feature. For your particular use-case, is the current system of sub-feature privileges granular enough, or would you need to make this decision on a dashboard-by-dashboard (or visualization-by-visualization) basis? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#73192 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANLEQORDEVUMBCPNIIQJLMLR522TZANCNFSM4PGRRF3Q>. == This message is confidential. It may also be privileged or otherwise protected by work product immunity or other legal rules. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. The integrity and security of this message cannot be guaranteed on the Internet. Enable-U, Asterweg 19D11, 1031 HL Amsterdam, www.enable-u.com<http://www.enable-u.com/>

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[ThomThomson]

This enhancement request could be fullfilled by Phase 3 of the Controls project, where we plan to allow Dashboard Authors to selectively hide pieces of the unified search bar.

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[ThomThomson]

Closing this in favour of #137560