Object Security for Asset Conditions in DA Units

The following table lists the types of users in a Platform configured for Delegated Administration and describes their access to Asset Conditions:

Note: Asset Conditions are visible across DA Units, as long as the DA user groups have the appropriate privileges. To prevent DA users from seeing or changing Asset Conditions, make sure that their DA user groups do not have the following privileges: Configuration - Asset Condition - Add and Configuration - Asset Condition - Modify. To run a SetAssetCondition action from an Asset dashboard, users need two privileges, Configuration - Asset Condition - Modify and Service - ExecuteActions. If a user has the Service - ExecuteActions privilege but not the Configuration privileges for Asset Conditions, an action to set the asset condition appears in the Asset dashboard but the user cannot run it.

 

User

Access

Principal Axeda® Connected Product Management Applications Administrator

Access to ALL Asset Conditions in the Platform

Non administrator with correct privileges

In the Configuration application, with appropriate privileges, this user can view, create, modify, and delete Asset Conditions. With the appropriate privileges to the Axeda® Service application, this user can run an action that changes the current asset condition (from the Asset dashboard).

1st level DA (DA1)

2nd level DA (DA11)

Another DA user within same DA as DA1

Same as non-admin user.