kibana-own-home icon indicating copy to clipboard operation
kibana-own-home copied to clipboard

Is it possible to hide personal indices and only show public ones?

Open thekofimensah opened this issue 6 years ago • 2 comments

If I have userA with access to .kibana_userA and .kibana_public by default, is there someway to remove his access to his own .kibana index (.kibana_userA)? I know I can remove his access via access control rules, but it would be cool if it didn't even appear in the own_home app so my end user doesn't see that they have their own index and they only have access to one of 3 public indices.

I want to have users that their default index will be one of 3 public indices but not their private one. Users will be displayed a set of dashboards for their public index, but filtered by their own relevant data (via DLS). There will be several users in each public index, but they won't be able to see each other's data, just their own via filtered access controls (DLS). Any guidance on how to do this effectively?

thekofimensah avatar Apr 21 '18 15:04 thekofimensah

What about this patch?

For example, you can use own_home.personal.enabled option as follows:

. . .
own_home.personal.enabled: false
own_home.local.groups: [ public, sandbox ]
own_home.default_kibana_index_suffix: public

With the above settings, each user will not have personal kibana.index.

wtakase avatar Apr 23 '18 04:04 wtakase

@wtakase Just tested this with 6.2.4 and the Personal tenant header is still appearing with the user underneath it. What changes is that the default index is no longer the personal index and I can't actually change to the personal index (both are good things). But I'd imagine you'd want that header and section to disappear for this use case because they're not needed.

thekofimensah avatar May 04 '18 19:05 thekofimensah