The following table lists the types of users in a Platform configured for Delegated Administration and describes their access to Locations:
Important! Editing the Organization and Location of an asset from the Axeda® Service application can change the access to the asset. Consider restricting the users who have the privilege to edit this information from the Service application.
NOTE: DA visibility restrictions and privileges are NOT fully supported for Locations. See Supported Objects for Delegated Administration for more information.
In this table, "accessible assets" refer to the assets that the user can access, based on the asset groups assigned to the user's user group.
User |
Access |
Principal Axeda® Connected Product Management Applications Administrator |
Access to ALL Locations in the Platform |
Non administrator with correct privileges |
In Configuration Application -> Organizations -> View, Edit Locations, assuming correct user group privileges Access to Locations that this user created AND to locations associated with accessible assets. Assuming appropriate privileges: Example 1: if this user has access to asset 1 in Org 1 at Location B, the user can view and edit Org1 and Location B from the Configuration application. Example 2: if this user creates Org2 and Location C, this user can view and edit Org2 and Location C in the Configuration application. Example 3: if the system administrator (Principal user) created Location A in Org3, this user cannot see it unless he/she can see one or more assets associated with Org3. In the Service Application, a user can see all Organizations and Locations for each accessible asset. |
1st level DA user (DA1) 2nd level DA user (DA1-1) Another DA user within same DA as DA1 |
Same as Non-admin with correct privileges. The only way a DA user can see a Location created by a child-DA user is if the DA user has access to the child-DA's asset. A DA user in DA1 cannot see Locations created by a DA user in another DA at the same level (DA2), unless for some reason the user in DA1 has access to assets in DA2. |