Skip to content

fixup notes around enabling & disabling #1129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
May 27, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 31 additions & 6 deletions source/customizations.rst
Original file line number Diff line number Diff line change
Expand Up @@ -9,15 +9,21 @@ Customizations

.. _disabling_applications:

Disabling Applications
----------------------
Enabling and Disabling Applications
-----------------------------------

OnDemand is comprised of a few components. Each of which you can disable or limit
access by simply changing the file permissions of the application.
OnDemand is comprised of a few components. Each one you can disable or limit
access by simply changing the file permissions of the application. The application
will only be available if regular users can read the files. When they cannot
read the files, the application is disabled. When they can, it is enabled.

All the applications OnDemand installs are located in ``/var/www/ood/apps/sys``.
So, for example, if you wished to disable the file browser you would simply
change its directory to 700 so it's unreadable by regular users.

Disabling Applications
......................

So, for example, if you wished to disable the file browser for all users
you would simply change its directory to 700 so it's unreadable by regular users.

When this directory is unreadable by regular users, the functionality
it provides will be disabled.
Expand All @@ -26,6 +32,9 @@ it provides will be disabled.

sudo chmod 700 /var/www/ood/apps/sys/files

Enabling Applications for a limited number of users
...................................................

Alternatively, if you wished to limit access you can do so through group
permissions. For example, if you wanted to limit access to the file browser
to only members in the Unix group ``staff``, you would simply apply the
Expand All @@ -37,6 +46,22 @@ directory while members of the ``staff`` Unix group can.
sudo chmod 750 /var/www/ood/apps/sys/files
sudo chown root:staff /var/www/ood/apps/sys/files

This ensures:

* The application is readable and executable by the staff group.
* All other users not in staff group will not see or access it.

.. _enabling_applications:

Enabling Applications
.....................

Conversely, if the directory is already ``700`` just reverse the process to
enable the application. Set the directory to ``755`` to *enable* it for all users.

.. code-block:: sh

sudo chmod 755 /var/www/ood/apps/sys/projects

.. _configure_announcements:

Expand Down
4 changes: 2 additions & 2 deletions source/release-notes/v4.0-release-notes.rst
Original file line number Diff line number Diff line change
Expand Up @@ -331,8 +331,8 @@ it's not feature rich enough to replace the Job Composer in this release.

However, you may still wish to enable this for staff members or friendly users.

To enable the Project Manager, simply follow the instructions in :ref:`disabling_applications`
to enable this application.
To enable the Project Manager, refer to the instructions in the
:ref:`enabling_applications` section.

Upgrade Instructions
--------------------
Expand Down