Custom properties
Custom properties let you organize customers and devices using your own unique identifiers, such as text, dates, URLs, or predefined lists. You use these properties to filter objects, target N-central rules, and drive automated workflows.
Custom properties enable you to categorize devices and customers by unique identifiers. You can use custom device properties as filterable items so you can apply N-able N-central rules for automated workflows with devices and customers, based on devices having or not having a specific custom property and values.
You can apply custom properties at the Service Organization (SO), customer, site, or device level. Properties added at a higher level automatically apply to lower levels. For example, a property added at the Service Organization level applies to all customers in that organization, while a property added at the customer level applies only to that customer.
Custom properties work with Automation Manager policies to pass customer or device-specific values into tasks. This lets you reuse a single policy across multiple customers or devices instead of creating separate policies. Automation policies can also update device-level properties based on task outcomes. Automation policies cannot update customer-level properties.
You can associate custom properties with specific device classes and operating systems, or apply them to selected customers and sites.
To access custom properties, go to Administration > Custom Properties.
You can also use custom properties with Automation Manager policies that pulls in the appropriate customer or device-specific information, rather than creating separate Automation Manager policies per customer, or per device. Automation policies can also set the property for devices. For example, a policy can run based on a property of "Maintenance required". After completion of the task, the automation policy can change the property to "Maintenance completed. Automation policies cannot update customer-level properties.
Depending on what level you add the property, that property will filter down to each level. For example, if you add the custom device property at the Service Organization level, it will be added for all of the customers under that SO. If you add the custom property at the customer level, it will only be added for that customer.
Associate custom properties for specific device types. A custom property can be a URL, text, date or a drop-down list with a customized list of values. These properties are applied to devices based on their class and operating system, or selected customers and sites.
What do you want to do?