# Segregating Data Between Spaces in a Single Deployment

**URL:** <https://discuss.elastic.co/t/segregating-data-between-spaces-in-a-single-deployment/373370>\
**Category:** Logstash\
**Created:** [January 19, 2025, 9:18pm UTC](https://discuss.elastic.co/t/segregating-data-between-spaces-in-a-single-deployment/373370 "2025-01-19T21:18:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Core990](https://avatars.discourse-cdn.com/v4/letter/c/76d3ee/32.png) [@Core990](https://discuss.elastic.co/u/Core990)\
**Post date:** [January 19, 2025, 9:18pm UTC](https://discuss.elastic.co/t/segregating-data-between-spaces-in-a-single-deployment/373370/1 "2025-01-19T21:18:52Z")

</div>

Hello,

I have a use case where I want to create multiple spaces in a single Elastic deployment, and I need to ensure strict data segregation between these spaces. Specifically:

1. I want the logs collected by agents in Space 1 to be completely invisible to Space 2 and Space 3, and vice versa.
2. Each space should only handle and view the logs meant for that space, with no overlap or access to other spaces' data.

---

<div class="post-metadata">

**Author:** ![Core990](https://avatars.discourse-cdn.com/v4/letter/c/76d3ee/32.png) [@Core990](https://discuss.elastic.co/u/Core990)\
**Post date:** [January 19, 2025, 9:24pm UTC](https://discuss.elastic.co/t/segregating-data-between-spaces-in-a-single-deployment/373370/2 "2025-01-19T21:24:26Z")

</div>

@stephenb  
Hi,  
Can u help me here ?  
Thanks .

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [January 19, 2025, 11:47pm UTC](https://discuss.elastic.co/t/segregating-data-between-spaces-in-a-single-deployment/373370/3 "2025-01-19T23:47:47Z")

</div>

Hi @Core990 Welcome to the community.

A couple of process items first.

Please be patient. There are many questions and few to answer. I see you posted and then asked for help 5 mins later, which is not encouraged...

This brings us to the second item: it is not good forum etiquette to `@` people who are already not part of the topic, this is definitely not encouraged and I will not respond to that next time.

With respect to your topics, I would suggest you read our official documentation as there are some good examples / direction

> **[Securing access to Kibana | Kibana Guide \[8.17\] | Elastic](https://www.elastic.co/guide/en/kibana/8.17/tutorial-secure-access-to-kibana.html)**

> **[Kibana role management | Kibana Guide \[8.17\] | Elastic](https://www.elastic.co/guide/en/kibana/current/kibana-role-management.html)**

With respect to using an elastic agent, you can add / specify the namespace and then use that with the Kibana / Spaces management to segment the data.

> **[Data streams | Fleet and Elastic Agent Guide \[8.17\] | Elastic](https://www.elastic.co/guide/en/fleet/current/data-streams.html)**

Give it a try and come back with some specific questions.