Does setting the Rhodecode user to "no login" negatively effect functionality

To harden our environments we have been asked to update the Rhodecode user to “/sbin/nologin”. Our concern is that even if testing shows no immediate issues, there could be unforeseen and insidious issues that aren’t instantly identifiable. Could updating this setting cause negative impacts on the application’s functionality?

We are currently running RhodeCode Enterprise 4.12.4 Community Edition on a RHEL 6 VM.

In our view there’s nothing in our system that would break because of that change, so we consider it safe.