User

RR detects the name of your Windows/Linux/Mac user if you use the rrSubmitter or rrControl.

Project

Multiple user are working on the same project.
But you have set that "Anonymous" is allowed to change his jobs only.
For this case, please create a rrLogin with the projects name and assign a password.
The next time a user wants to change a job of an other user, rrControl asks for the password of the project.

Render App

Works similar to Project.
Can be used if you have for example someone responsible for all Nuke Compositings in your company. 

RR Admin

The master password.
It can be used for anything.

Note that you can add an "RR admin right" to other rrLogins as well if you 

• do not want to spread the master password 
• do not want to enter the RR admin password every time you need it in rrControl
  As rrControl can detect who is logged in at the machine.

Anonymous

This applies to any user that does not exist in RR.

rrScriptAuth

The rrClient support an authorization token for the job that is currently executed on the rrClient.
It can be used to run a script that sends commands to the rrServer for that job.
This way a job can even delete itself.
Please see for example the Finished-Script RR\render_apps\_prepost_scripts\Finished99__DeleteJob.cfg

New User Template

If someone creates a new user, it gets these rights

Default Group

If someone creates a new user, it is added to this group.

Encode Jpegs

If the jpegs are encoded, then they can only be seen in rrControl  and  only if the user has the right to see the jobs details.

Without the job details it is not possible to decode the image.

Hide job if artist cannot list files in project path on fileserver

If you have confidential projects that not everyone is allowed to view, then you have probably restricted the access to the project files on your fileserver.

rrControl can use this fileserver restriction to hide the information of these jobs.
If the user cannot view files, then rrControl cannot view the files and hides the job information.

rrConfig

All tabs are locked beside the rrLogin and Client Group Tab.
Anybody can add a new user (but not change any setting of existing users).
And anybody can add/change client groups.

Unlock for OS user logged in without authorization

ON: If you have added the name of your OS login (Windows, Linux, Mac) as rrLogin 
and if this user has the rrAdmin or rrConfig right, then rrConfig automatically unlocks itself.
Security Note: There are ways to fake user accounts before rrConfig is started on any machine.

OFF: You have to unlock rrConfig with your rrLogin password.

rrClient Close

The rrClient menu command "Close Client" requires an rrAdmin password

Authorization required

OFF (default): rrControl takes the user of the OS login (Windows, Linux, Mac). 
There are ways to fake user accounts before rrControl is started on any machine.

ON: rrControl does not takes the OS user automatically.

The artist has to login in rrControl. 
Note that you are able to remember the rrLogin authorizaton on the machine within its user settings/registry.

Note: This setting is for your intranet only. Remote connections always require authorization.

If you do not set an IP whitelist, then all connections are considered as "local". Please see next setting.

Restrict Local Intranet to: (IP starts with)

The IP is used by the rrServer to detect if a connection is coming from the local intranet or from outside (if you have for example multiple subnets for different offices or if you have forwarded the port through your router).

Multi-user login for fileserver.

You should not need this settings for a company network.
This setting is for special networks only in which you do not have a user that can access all projects
Do not enable it if you have not been advised by the RR Support.