[Spaces] Role page should be global and not Space specific

[AlonaNadler]

Currently, when configuring a new role, it only allows setting the index patterns of the space the admin is currently at, that's a problem since if there is a role that needs to have the privilege to index patterns in multiple spaces it's not possible to configure this role.
Example:
There are only 2 spaces:

• Engineering has index pattern A
• Product has index pattern B

When I want to configure a role that will have a privilege for both index pattern A and B I can't do it.
Role page shouldn't be space specific it should be global

cc: @elastic/kibana-security

[legrego]

This raises an interesting challenge if the admin configuring roles does not have access to all Spaces (and therefore, all index patterns).

Technically, a user only needs the Elasticsearch manage_security permission, and read access to at least one space to create roles through the Kibana UI/API.
Given that, I think we'll need to come up with a way to only show index patterns that exist within the Spaces the current user has access to.

I'm going to block this on #21995 since we need secured spaces to exist before we can make progress here.

[kobelb]

For us to address this cleanly and universally, I think we're going to have to add the ability to search for saved objects across spaces, which isn't something we were planning on having to do with the first phase of Spaces. I'd prefer if we address this deficiency in a later phase to ensure we don't introduce a hacky temporary solution and have the time to fully implement this appropriately.

[jimgoodwin]

I think this is a bit misleading. These roles relate to Elasticsearch Indexes not Kibana Index Pattern Objects. What we should be listing here are all of the Elasticsearch Indexes this administrator can see. I get the motivation to use Index Patterns as a shortcut to help them choose something, but in reality they're just choosing that wildcard pattern, not the object itself. I'd be in favor of (in the future) showing the index patterns that they can see, followed by all matching indexes for what they've typed so far after say two or three letters. This is also in my opinion broken in the existing product, so I don't think it needs to be enhanced/corrected immediately.

[kobelb]

I think this is a bit misleading. These roles relate to Elasticsearch Indexes not Kibana Index Pattern Objects. What we should be listing here are all of the Elasticsearch Indexes this administrator can see. I get the motivation to use Index Patterns as a shortcut to help them choose something, but in reality they're just choosing that wildcard pattern, not the object itself. I'd be in favor of (in the future) showing the index patterns that they can see, followed by all matching indexes for what they've typed so far after say two or three letters. This is also in my opinion broken in the existing product, so I don't think it needs to be enhanced/corrected immediately.

That's a good point, and I think that listing the index patterns in additional to the actual indices in Elasticsearch would be the ideal user experience.

[legrego]

We were previously blocked on our inability to search across spaces (#27003), but this has since been resolved (#67644).

With this out of the way, our next steps would be to collaborate on a design to effectively show index patterns ("data views") alongside indices and data streams in an understandable UX, and then prioritize the work to implement this new design.

[legrego]

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.