# Media set marking propagation

**URL:** <https://community.palantir.com/t/media-set-marking-propagation/1096>\
**Category:** Ask the Community\
**Tags:** media-sets\
**Created:** [August 21, 2024, 1:11pm UTC](https://community.palantir.com/t/media-set-marking-propagation/1096 "2024-08-21T13:11:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matija](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/matija/32/236_2.png) [@Matija](https://community.palantir.com/u/Matija)\
**Post date:** [August 21, 2024, 1:11pm UTC](https://community.palantir.com/t/media-set-marking-propagation/1096/1 "2024-08-21T13:11:43Z")

</div>

Is there a way to stop requiring an organization marking on a media set?

---

<div class="post-metadata">

**Author:** ![bduffield](https://avatars.discourse-cdn.com/v4/letter/b/c67d28/32.png) [@bduffield](https://community.palantir.com/u/bduffield)\
**Post date:** [August 22, 2024, 2:32pm UTC](https://community.palantir.com/t/media-set-marking-propagation/1096/2 "2024-08-22T14:32:10Z")

</div>

How does the media set get the organization marking? Is this media set created/updated via a transform?

Generally media sets shouldn’t behave any differently here to datasets, and so take the same approaches to manage markings.

e.g. you can use the same `stop_propagating` and `stop_requiring` syntax on media set inputs - https://www.palantir.com/docs/foundry/platform-security-management/manage-markings/#remove-an-inherited-marking

but not entirely sure that does what you need

Any chance you can explain in more detail your end-to-end workflow/what you’re trying to achieve?

---

<div class="post-metadata">

**Author:** ![Matija](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/matija/32/236_2.png) [@Matija](https://community.palantir.com/u/Matija)\
**Post date:** [August 22, 2024, 4:39pm UTC](https://community.palantir.com/t/media-set-marking-propagation/1096/3 "2024-08-22T16:39:17Z")

</div>

Yep, using the same `stop_requiring` as on datasets worked even though it’s not documented anywhere. Thanks for suggesting it.
