Restrict access to groups of saved objects in Kibana

[elasticmachine]

Original comment by @tbragin:

Common request, but he haven't been tracking an issue for this in x-pack-kibana, instead relying on an old OSS issue for tracking (#4453).

The user scenario is -- as a Kibana admin, I want to to group or tag saved objects in a Kibana instance or Kibana Space (dashboards, visualizations, saved searches, index patterns), and specify which users/roles have access to those objects and what level of access (read-only, read/update, delete, etc..)

[elasticmachine]

Original comment by @epixa:

@tbragin I'm interested to see spaces get into people's hands before we start evaluating how useful something like this would be in addition to that. I suspect the vast majority of people that want this would be satisfied enough with spaces, but we can't say for sure until people start using them.

If necessary, I do have an idea about "projects" within Kibana that can be used to organize a bunch of different saved objects together in a visual way, which might also be an option here. I wasn't necessarily thinking about them as a security feature outright, but it's possible.

[kobelb]

Closing this as Spaces is our current solution for this problem.