# Creating lifecycle policies in default space

**URL:** <https://discuss.elastic.co/t/creating-lifecycle-policies-in-default-space/371287>\
**Category:** Elasticsearch\
**Created:** [December 2, 2024, 2:37am UTC](https://discuss.elastic.co/t/creating-lifecycle-policies-in-default-space/371287 "2024-12-02T02:37:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![searchwithme](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/searchwithme/32/137075_2.png) [@searchwithme](https://discuss.elastic.co/u/searchwithme)\
**Post date:** [December 2, 2024, 2:37am UTC](https://discuss.elastic.co/t/creating-lifecycle-policies-in-default-space/371287/1 "2024-12-02T02:37:11Z")

</div>

Hello team! If I modify or create lifecycle policies in default space will they be accessible in my “engineering” space? In other words, is it a recommendation to make changes to policies in default space and then have them associated to my deployments in a different space (are the policies visible from other spaces)

---

<div class="post-metadata">

**Author:** ![sholzhauer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sholzhauer/32/110282_2.png) [@sholzhauer](https://discuss.elastic.co/u/sholzhauer)\
**Post date:** [December 2, 2024, 9:59am UTC](https://discuss.elastic.co/t/creating-lifecycle-policies-in-default-space/371287/2 "2024-12-02T09:59:09Z")

</div>

lifecycle policies exist on the "elasticsearch" level. Making adjustments within your default space will therefore also be reflected on the API and within other spaces.