How to Assign Permissions to System Tables

ArcFM geodatabases contain the following essential tables, which are created by running the Create/Update ArcFM Solution System Tables function:

• MM_CLASS_MODELNAMES

• MM_DOCUMENTS

• MM_EDITED_FEATURES

• MM_FIELD_MODELNAMES

• MM_MOBILE_IMPORT_ORDER

• MM_PACKAGES (also MM_HIDDEN_PACKAGES if available)

• MM_PAGE_TEMPLATES

• MM_PERSIST_INFOMM_QAQC

• MM_SNAPPING

• MM_STORED_DISPLAYS

• MM_SYSTEM_DOCUMENTS

• MM_SYSTEM_PACKAGES

• MM_SYSTEM_PAGE_TEMPLATES

• MM_SYSTEM_PERSIST_INFO

• MM_SYSTEM_STORED_DISPLAYS

These tables store important configuration information for the use and management of Stored Displays, model names, snapping, etc.

Permissions to these tables should be assigned to two roles: 

• The mm_admin role should be assigned Write permission to all these tables. 

• The mm_user role's permissions should be as follows:

  • Read:

    • MM_CLASS_MODELNAMES

    • MM_FIELD_MODELNAMES

    • MM_MOBILE_IMPORT_ORDER

    • MM_QAQC

    • MM_SNAPPING

    • MM_SYSTEM_DOCUMENTS

    • MM_SYSTEM_PACKAGES

    • MM_SYSTEM_PAGE_TEMPLATES

    • MM_SYSTEM_PERSIST_INFO

    • MM_SYSTEM_STORED_DISPLAYS

  • Write:

    • MM_DOCUMENTS

    • MM_EDITED_FEATURES

    • MM_PACKAGES (also MM_HIDDEN_PACKAGES if available)

    • MM_PAGE_TEMPLATES

    • MM_PERSIST_INFO

    • MM_STORED_DISPLAYS

As always, assigning these table permissions should be performed in ArcCatalog and the database should be backed up before any changes are made.