# Sharing resources (Data views and Dashboards) across Spaces

**URL:** https://discuss.elastic.co/t/sharing-resources-data-views-and-dashboards-across-spaces/312933
**Category:** Kibana
**Created:** [August 25, 2022, 2:23pm UTC](https://discuss.elastic.co/t/sharing-resources-data-views-and-dashboards-across-spaces/312933 "2022-08-25T14:23:03Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![yelloyonder](https://avatars.discourse-cdn.com/v4/letter/y/5fc32e/32.png) [@yelloyonder](https://discuss.elastic.co/u/yelloyonder)
#### Post date: [August 25, 2022, 2:23pm UTC](https://discuss.elastic.co/t/sharing-resources-data-views-and-dashboards-across-spaces/312933/1 "2022-08-25T14:23:04Z")

</div>

Hi,

I've been trying to setup Spaces in Kibana (Elastic cloud) for non-admin teams so they only see the Kibana resources they need e.g. Discover and Dashboards under Analytics and not Security.

When moving to the new Space and accessing for example Discover, I see a message  
" You have data in Elasticsearch. Now, create a data view. "

If I recreate a Data VIew, I then get access to it. The same occurs with Dashboards.

I've created 100+ Discover views and Dashboards and it seems strange that I would need to export them from the original Space and import them into a new Space. Maybe I'm using Spaces incorrectly but I wouldn't have thought it would be unusual to just want to hide menu options from users and not have to recreate or import lots of objects.

For testing the user has the _superuser_ role and the All privileges allow across all resources.

Can anyone advise ?  
Thanks

---

<div class="post-metadata">

### Author: ![yelloyonder](https://avatars.discourse-cdn.com/v4/letter/y/5fc32e/32.png) [@yelloyonder](https://discuss.elastic.co/u/yelloyonder)
#### Post date: [August 26, 2022, 8:56am UTC](https://discuss.elastic.co/t/sharing-resources-data-views-and-dashboards-across-spaces/312933/2 "2022-08-26T08:56:26Z")

</div>

To reply to myself, I see I need to share or copy Saved Objects across the Spaces. Which makes sense just not what I was expecting.

---

<div class="post-metadata">

### Author: ![jughosta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jughosta/32/107160_2.png) [@jughosta](https://discuss.elastic.co/u/jughosta)
#### Post date: [September 5, 2022, 8:12am UTC](https://discuss.elastic.co/t/sharing-resources-data-views-and-dashboards-across-spaces/312933/3 "2022-09-05T08:12:52Z")

</div>

Hi @yelloyonder !  
I would recommend to start from creating a new user role and customize privileges to Kibana features this way [Kibana role management | Kibana Guide [8.4] | Elastic](https://www.elastic.co/guide/en/kibana/current/kibana-role-management.html#adding_kibana_privileges)

---

<div class="post-metadata">

### Author: ![yelloyonder](https://avatars.discourse-cdn.com/v4/letter/y/5fc32e/32.png) [@yelloyonder](https://discuss.elastic.co/u/yelloyonder)
#### Post date: [September 29, 2022, 1:10pm UTC](https://discuss.elastic.co/t/sharing-resources-data-views-and-dashboards-across-spaces/312933/4 "2022-09-29T13:10:06Z")

</div>

Thanks! (apologies for slow reply)

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 27, 2022, 1:10pm UTC](https://discuss.elastic.co/t/sharing-resources-data-views-and-dashboards-across-spaces/312933/5 "2022-10-27T13:10:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
