Hello.
Most (but not all) user licenses are based upon concurrency of usage - ie, you can use a system so long as no-one else is using it at the same time.
If you could guarantee that only one user would be able to access the system at a time then you'd be on firmer ground because it would be the same as those users sending you the source code to compile for them. However...trust of that sort is a BIG ask as it could easily be abused.
I would say it's unlikely you're going to get the go-ahead to do it unless, as Grey suggests, BRL come up with a multi-user license.
Goodbye.
Most (but not all) user licenses are based upon concurrency of usage - ie, you can use a system so long as no-one else is using it at the same time.
If you could guarantee that only one user would be able to access the system at a time then you'd be on firmer ground because it would be the same as those users sending you the source code to compile for them. However...trust of that sort is a BIG ask as it could easily be abused.
I would say it's unlikely you're going to get the go-ahead to do it unless, as Grey suggests, BRL come up with a multi-user license.
Goodbye.