Hello Ross,
Thank you for your message.
When you set user 2 to no access to computer B you effectively only tell the program not to show the computer B record in user 2 address book. However, they can still access the remote Host (computer B) if they know access credentials for that Host.
In other words, address book access rights and Host access rights are two different independent things. But you can combine them (see option 2 below).
There are two options to resolve that:
1) Change security settings on the Host. For example,
create user accounts on each Host and then if you need to prevent a certain user from accessing a Host just disable their account on that specific Host.
2) Use the "authorization server" role of the RU Server. This is described
here (see "Authorization role" section) and we'll also soon update our documentation with detailed instructions on how to set up
custom server security as we call it.
With option two properly configured your users will only have to sign in their Viewer to be able to access the Hosts. The advantage of using auth server option is that you can centrally manage Host permissions and change them in one place instead of having to change security permissions on each Host (as is with option 1).
Sorry for the lack of documentation on setting up auth server, it will be available very soon and appear
in this chapter. Feel free to ask any questions you might have.
Thanks.
