Security Tables
The following Database Diagram shows six tables that are used by MM .NET for defining and enforcing end user security in both Windows and Web applications:

Here is a description and structure of each table:
Note: You can add new fields to the security tables without affecting MM .NET. However, if you change the name of a field, you must also make a change to the corresponding security business object. For details, see the Help topic Security Business Objects.
Users
Contains all users who have access to the application.
Note that if you run the MM .NET SQL Script to create the Users table it adds a LanguageFK column to the table. This column is used in applications that implement MM .NET Localization. If you have no need for this column, you can remove it.
Roles
Specifies the different roles of users such as Administrator, Manager, Accountant, and so on.
UserRoles
A many-to-many link table that specifies the roles a user belongs to.
Security
Identifies all secure objects in the application, providing a unique primary key (a GUID) and an associated description.
UserSecurity
A many-to-many link table that specifies the access level (none, read-only, full) a user has to a secure object.
RoleSecurity
A many-to-many link table that specifies the access level (none, read-only, full) a role has to a secure object
Referential Integrity
The MMSecurity.sql script adds referential integrity for cascading deletes in the security tables. Here are the constraints that are automatically added for you:Users.UserPK --> UserRoles.UserFK --> UserSecurity.UserFK Roles.RolePK --> UserRoles.RoleFK --> RoleSecurity.RoleFK Security.SecurityPK --> UserSecurity.SecurityFK --> RoleSecurity.SecurityFKSo, for example, if you delete a user from the Users table, any records for that user in the UserRoles and UserSecurity table are automatically deleted.
Setting up the Security Database
For information on setting up the security database, see the Help topics Specifying the Security Database and Adding Security Tables to your Application Database.© (c) 2026 Oak Leaf Enterprises, Inc., 1996-2026 • Updated: 04/26/18
Comment or report problem with topic
