The modUserList table, located in the modSystem database, contains the list of all solution database users on the server.
A modUserRoles table, located in each team solution, stores information that associates users in the modUserList table with the roles to which they belong. The user's SAMAccountName is tied to a RoleName in the team solution.
Each team solution contains a view called modUserList that contains a subset of the user directory for users of the particular team solution. This view is based on the modUserList table in the modSystem database, and its recordset is limited using the relationship between SAMAccountName column in the modUserRoles table to the SAMAccountName column in the modUserList column.
When a team solution is taken offline, a snapshot of the modUserList view is created as the modUserList table in the offline database. This offline version of the modUserList table makes it possible for user information lookups to work while not connected to the network.
Any code or lookups created against the modUserList object continue to work properly while offline. For this reason, it is very important to develop against the view of modUserList, rather than the modUserList table in modSystem.
Note Every time you synchronize the user directory, the modUserList table in the modSystem database is updated to remove any users no longer in your team solution databases and to revise existing user information.
Any SQL Server users who have been assigned to a role in your solution are added to the modUserRoles table in your team solution and are displayed in the modUserList view.
If the team solution is being used offline when the user directory is synchronized, users added to the solution are not available in the offline database until it has been synchronized with the online database.