Users File Integrity

A consequence of #74 occurs to me.

If we inject the users file from our `T:/` drive when we build the code, we will be replacing the file that exists on in the respective web server once the new code bundle is deployed.

In our manual deploy process, this means we need to pull the users file from the appropriate deployment instead of picking it from the `T:/` drive before building the code.

We need to ensure manual and automated deploy processes take this into account. We should have some way ensuring the integrity of this file.

Start by tracing the manual and automated deployment processes and locating where the users file is selected or injected. Done means both processes preserve the appropriate deployed users file rather than unintentionally replacing it from the T:/ drive.

Written by the indexing model from the issue text.