TPRM and the Explicit Roles plugin

Release version: Australia

Updated March 12, 2026

2 minutes to read

Summarize

Summarized using AI

Summary of TPRM and the Explicit Roles plugin

The activation of the Third-party Risk Management (TPRM) plugin includes the installation of the Explicit Roles plugin, which is essential for managing user access. Administrators use this plugin to assign thesncinternalandsncexternalroles, controlling access for internal and external users to the instance and its resources.

Show full answer Show less

Key Features

Role Assignment: When third-party contacts are created, they are automatically assigned the sncexternal role, granting them access to the Third-party portal.
Role-based Access Control: The Roles field in various tables determines user access. If this field is empty, all users can access the record.
Automatic Role Updates: Upon installation of the Explicit Roles plugin, the Roles field is updated for Service Catalog items, granting sncinternal access to existing users and requiring new users to be assigned this role for access.

Key Outcomes

After implementing the Explicit Roles plugin:

All existing records with an empty Roles field are assigned the sncinternal role, restricting access to only users with this role.
Newly created records will have the sncinternal role assigned automatically if the glide.sc.useusercriteria property is set to false.
For records such as ACLs, catalog items, and reports, the sncinternal role is consistently applied to ensure controlled access.

Activating the Third-party Risk Management plugin also installs the Explicit Roles plugin. Administrators assign the snc_internal and snc_external roles to provide internal and external users access to the instance.

When third-party contacts are created, they are automatically assigned the snc_external role, giving them access to resources related to the Third-party portal.

Various tables provide role-based access to record by setting the Roles field. If the Roles field is empty, all users have access to that record. For example, if the Roles field for a Service Catalog item has an empty Roles field, all users have access to that Service Catalog item.

However, when the Explicit Roles plugin is installed, the Roles field is updated to snc_internal. Also, all users are given the snc_internal role. Continuing with the previous example:

Before installing the Explicit Roles plugin, if a Service Catalog item had an empty Roles field, it was accessible to every user.
After installing the Explicit roles plugin, the Roles field of the Service Catalog item is updated to snc_internal and all existing users are given the snc_internal role, making the catalog item accessible to those users.
After that, all new users must be assigned the snc_internal role, or they will not have access to that Service Catalog item.

The following table describes the changes to tables affected by the Explicit Roles plugin.

Table 1. Tables affected by the Explicit Roles plugin
Table	Changes
Access Control [sys_security_acl]	For all existing and newly created ACLs without a role requirement, the snc_internal role is assigned.
Catalog item [sc_cat_item]	For all records where the Roles field is empty, the snc_internal role is added. If the glide.sc.use_user_criteria property is set to false, newly created catalog items are automatically assigned the snc_internal role. If the property is set to true, the SNC External user criteria is added to all newly created catalog items, excluding external users from viewing the record.
Page [content_page]	For sites that have a login page, where the Read roles field is empty, the snc_internal role is added. For sites that have no login page or that have automatically created content pages, the public role is added.
Navigation Menu [sys_app_application]	For all records where the Roles field is empty, the snc_internal role is added. Newly created navigation menus with an empty Roles field are also automatically assigned the snc_internal role.
Overview Help Panel [sys_ui_overview_help_panel]	For all records where the Roles field is empty, the snc_internal role is added. Newly created overview panels with an empty Roles field are also assigned the snc_internal role.
Portal Page [sys_portal_page]	For all records where the Read roles field is empty, the snc_internal role is added. Newly created portal pages with an empty Read roles field are also automatically assigned the snc_internal role.
Processor [sys_processor]	For all records where the Roles field is empty, the snc_internal role is added. Newly created processors with an empty Roles field are also automatically assigned the snc_internal role.
Report [sys_report]	For all records where the Roles field is empty, snc_internal is added. Newly created reports that have an empty Roles field when sharing are also automatically assigned the snc_internal role.