Object Security for Contacts in DA Units

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

NOTE: DA visibility restrictions and privileges are NOT fully supported for Contacts. See Supported Objects for Delegated Administration for more information.

 

User

Access

Principal Axeda® Connected Product Management Applications Administrator

Access to ALL Contacts in the Platform

Non administrator with correct privileges

In the Configuration Application -> Contacts -> View and Edit, assuming correct privileges.

Access to all Contacts associated with Organizations that this user can access.

For example if this user has access to Org1, this user can view and edit all contacts in Org1.

If this user has the correct privileges to the Axeda® Service Application, this user should be able to View All contacts associated with an asset, add/remove contacts for the asset, but should NOT be able to edit a contact that is in an organization that this user cannot see.

For example: Asset1 is in Org1 but is associated with Contact1 from Org2. The user does not have access to Org2. In this situation, this user should not be able to edit Contact1 because this user does not have access to the contact's organization.

 

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 view and edit Contacts created by a user in a child DA Unit is if the DA user has access to the assets of the child DA Unit and thereby to the Organizations and Contacts of the child DA Unit that are assigned to those assets.