Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

It is possible to set access permissions on a per-virtual-root basis. In this way, specific users can be granted access to certain directories without allowing everyone access or having to add the users to the Administrative groups.

To do this, set the UserListvalue for the appropriate virtual root with the list of users and groups who have access to it or are denied access to it. For more information, see Web Server Access Rights.

The following example shows how to allow users Lori Kane and Jane Clayton, and the SomeGroup group, but restrict the Tai Yee user and the villains group.

Copy Code 
UserList="LoriKane; JaneClayton;-TaiYee;@SomeGroup;-@villains"
Note:
The format "*" or "@*" allows all users, and "-*" or "-@*" denies all users.

The string is interpreted sequentially. In other words, if Lori Kane is a member of the Finance group, the following strings will allow her access to the server.

Copy Code 
LoriKane
@ Finance
@ Finance;LoriKane
LoriKane;@ Finance
@ Finance;- LoriKane
LoriKane;-@ Finance
LoriKane;- LoriKane
*;-LoriKane;-@ Finance

The following strings will restrict Lori Kane's access to the server.

Copy Code 
-LoriKane
-@ Finance
-LoriKane;@ Finance
-@ Finance; LoriKane
-LoriKane; LoriKane
-LoriKane;*
Note:
The * format indicates a group, and it must be used in the list. It is possible that parsers understand both @* and * format, but they always use @* syntax.

Note that administrators always have access to virtual roots with A set to 1, even if they are not on the user list for that root. This applies even if the administrators are denied access explicitly in the UserList value.

See Also