# Disabling controls in dashboard **URL:** \ **Category:** Kibana\ **Created:** [May 14, 2021, 2:03pm UTC](https://discuss.elastic.co/t/disabling-controls-in-dashboard/273027 "2021-05-14T14:03:21Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Alexandre.Bernier](https://avatars.discourse-cdn.com/v4/letter/a/e8c25b/32.png) [@Alexandre.Bernier](https://discuss.elastic.co/u/Alexandre.Bernier)\ **Post date:** [May 14, 2021, 2:03pm UTC](https://discuss.elastic.co/t/disabling-controls-in-dashboard/273027/1 "2021-05-14T14:03:21Z")
Hello there, I'm running the stack 7.10 and I would like to know if there is a way to disable a control in a dashboard? Since we can't pre-filter a control (issue [#17301](https://github.com/elastic/kibana/issues/17301)) to display a single value or exclude differents values, I am pre-selecting a value for my control in my dashboard. ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/8/18c329bfa15503db6579c77ab820e8ece849330a.png) The issue is that the user can change the selected value. Is there a way to prevent this? Actually, my data is in one index and I don't really want to split my data into 17 index (according to my use case). Best regards, Alexandre ---
**Author:** ![afharo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/afharo/32/75202_2.png) [@afharo](https://discuss.elastic.co/u/afharo)\ **Post date:** [May 14, 2021, 4:04pm UTC](https://discuss.elastic.co/t/disabling-controls-in-dashboard/273027/2 "2021-05-14T16:04:11Z")
Hi @Alexandre.Bernier, I'd like to better understand your use case. Do you want to have a dashboard with a specific filter applied that users can't change? I believe that you can do so by creating the visualizations with the filter internally applied. An alternative would be to limit what the users can see. If the users can only see the info for one department only, You could use the permissions to allow the user to only see the docs that match a certain query using the [Document-level security](https://www.elastic.co/guide/en/elasticsearch/reference/current/document-level-security.html) options. ---
**Author:** ![Alexandre.Bernier](https://avatars.discourse-cdn.com/v4/letter/a/e8c25b/32.png) [@Alexandre.Bernier](https://discuss.elastic.co/u/Alexandre.Bernier)\ **Post date:** [May 14, 2021, 6:17pm UTC](https://discuss.elastic.co/t/disabling-controls-in-dashboard/273027/3 "2021-05-14T18:17:07Z")
Hi @afharo, Thanks for the answer! Here's the full explanation of my use case: - I use only one index, let's say **test-** \* - In that index, I have multiple fields, but for the example: **Department** , **ProductGroup** and **Part**. **Department** and **ProductGroup** are use for the filtering. When we look at the documents, we see that a **Department** can have multiple **ProductGroup**. - In a dashboard, we create a chart displaying the number of document by **Part**. - We add two controls (filter). The first one is for the **Department** and the second one is for the **ProductGroup**. The **Department** is the parent of **ProductGroup**. - We give access to the user **Qwerty**. He's a member of **ZXCV** department. He can only see data from that department. We don't want him to see data from **AZERTY** department. - The chart has already an internal filter to display the data only for **ZXCV**. - **The issue start here.** - The user needs to be able to filter by **ProductGroup**. To filter the **ProductGroup** , we need to select a **Department** but the user is still able to change the **Department**. Ideally, it would be nice if I could only display the **ProductGroup** control filtered by a specific department in my dashboard, but we can't actually do that. We're not able to filter a control. For the document security level, that's a good one. I didn't know that we were able to do this. The only sad thing about that is that I'm running a basic license. Regards, Alexandre ---
**Author:** ![afharo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/afharo/32/75202_2.png) [@afharo](https://discuss.elastic.co/u/afharo)\ **Post date:** [May 18, 2021, 4:54pm UTC](https://discuss.elastic.co/t/disabling-controls-in-dashboard/273027/4 "2021-05-18T16:54:52Z")
Thank you for the explanation. I think you are right: Input Controls show every possible value, and it's not affected by any other filters. I also see you commented on [[Input Controls] Ability to Filter an Input Control · Issue #17301 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/17301), and I notice some activity from my colleagues around that issue. Hopefully, it'll be fixed soon. In the meanwhile, maybe [Filtered aliases](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-aliases.html#filtered) could work for you? Or considering bumping your subscription to make use of Document-level security 😜 ---
**Author:** ![Alexandre.Bernier](https://avatars.discourse-cdn.com/v4/letter/a/e8c25b/32.png) [@Alexandre.Bernier](https://discuss.elastic.co/u/Alexandre.Bernier)\ **Post date:** [May 18, 2021, 5:15pm UTC](https://discuss.elastic.co/t/disabling-controls-in-dashboard/273027/5 "2021-05-18T17:15:23Z")
Hey Alejandro! Happy to learn that there is some development around the issue! I will take a look at _Filtered aliases_. For now, short-term solution that I applied, I created an index by department. It's not cool but it's doing the work. If the _Filtered aliases_ do the job, I might change my setup again. Thanks for your help and have a nice day! 🙂 Alexandre ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 15, 2021, 5:15pm UTC](https://discuss.elastic.co/t/disabling-controls-in-dashboard/273027/6 "2021-06-15T17:15:30Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.