# Disabling built-in interactive apps

**URL:** <https://discourse.openondemand.org/t/disabling-built-in-interactive-apps/2288>\
**Category:** Get Help\
**Created:** [September 22, 2022, 8:33pm UTC](https://discourse.openondemand.org/t/disabling-built-in-interactive-apps/2288 "2022-09-22T20:33:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kilian](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/kilian/32/61_2.png) [@kilian](https://discourse.openondemand.org/u/kilian)\
**Post date:** [September 22, 2022, 8:33pm UTC](https://discourse.openondemand.org/t/disabling-built-in-interactive-apps/2288/1 "2022-09-22T20:33:36Z")

</div>

Continuing the discussion from [Any way to disable or shadow builtin apps (bc\_desktop)?](https://discourse.openondemand.org/t/any-way-to-disable-or-shadow-builtin-apps-bc-desktop/311/7):

Is there a better way to disable a default interactive app, other than changing permissions on RPM-provided directories? Modifying `/var/www/ood/apps/sys/` doesn’t seem like a very clean nor very robust approach. Wouldn’t it be better to allow local customization in `/etc/ood` to allow completely disabling apps?

---

<div class="post-metadata">

**Author:** ![travert](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/travert/32/3074_2.png) [@travert](https://discourse.openondemand.org/u/travert)\
**Post date:** [September 23, 2022, 2:21pm UTC](https://discourse.openondemand.org/t/disabling-built-in-interactive-apps/2288/2 "2022-09-23T14:21:11Z")

</div>

Hey, thanks for the question.

Currently that is still the way you would need to manage those default apps from displaying.

That said, you are correct in that it isn’t very robust because on each upgrade you will have to change those perms, which we realize is not ideal. Increasing granular customization like this is something we are putting work into and this is one of the things which will be added to that list.

There is now an associated GitHub issue specifically around this question:

> <https://github.com/OSC/ondemand/issues/2304>
>
> Regarding Discourse: https://discourse.openondemand.org/t/disabling-built-in-int…eractive-apps/2288
> 
> Is there a better way to disable a default interactive app, other than changing permissions on RPM-provided directories? Modifying /var/www/ood/apps/sys/ doesn’t seem like a very clean nor very robust approach. Wouldn’t it be better to allow local customization in /etc/ood to allow completely disabling apps?
> 
> 
> 
> ┆Issue is synchronized with this \[Asana task\](https://app.asana.com/0/1202821104799596/1203037726289758) by \[Unito\](https://www.unito.io)

Thanks for bringing this up! Please let us know if you have anymore questions or input.

---

<div class="post-metadata">

**Author:** ![kilian](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/kilian/32/61_2.png) [@kilian](https://discourse.openondemand.org/u/kilian)\
**Post date:** [September 23, 2022, 3:49pm UTC](https://discourse.openondemand.org/t/disabling-built-in-interactive-apps/2288/3 "2022-09-23T15:49:08Z")

</div>

Sounds great, thank you very much Travis!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex015/uploads/osc/original/2X/b/bae70bd0ed39a3ae769c2108155f4cb3e9da8385.png) [@system](https://discourse.openondemand.org/u/system)\
**Post date:** [March 22, 2023, 3:49pm UTC](https://discourse.openondemand.org/t/disabling-built-in-interactive-apps/2288/4 "2023-03-22T15:49:44Z")

</div>

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