Example 1: when an SMS server is configured to deliver SMTP messages, the recipient list is required to be a Named Email Address Group.
Example 2: if you allow the creation of an external SMS database you can restrict access to that database instance to only those members included in a specific Named IP Address Group.
The SMS client refers or requires one or more of these name resource types in each of the following areas:
Devices: Exception Rules, Servers, Management Routes
Events: IPS Events (Source and Destination Addresses)
Profiles: Restrictions and Exceptions (Source and Destination Addresses)
Responder: Policies (Inclusions and Exclusions)
Access to named resources functionality is based on user roles. Users with SuperUser capabilities can create or edit named resources; users with SuperUser or Admin capabilities can view named resources; users with Operator capabilities do not have access to named resources.
| Locked Resource | Description | User Capabilities |
| Unnamed Resources | Created automatically from user input and used for auto complete | Edit - No Delete - Yes |
| Named Resources | Created by the user | Edit - Yes Delete - Yes |
| Permanent Resources | Created by the SMS and not the user | Edit - No Delete - No |
Note: Named resources are used only on the SMS. In its communication with deviceS, the SMS sends only the constituent parts of a named resource (IP addresses, CIDR, and email address) to the device. The named resource itself is not sent.
Reference: SMS User Guide
