We have security profiles that have Editable access to Asset and Site. How do we restrict the ability to drag and drop on the Hierarchy views of these classes?
When using an unrestricted user or a user with full Editable access on classes that have Hierarchy views in the product, assets or sites may sometimes be drag and dropped by accident to a new location. Examples of such classes are Site and Asset, which we will illustrate here. Other classes that offer a hierarchy view include Cost types, Maintenance Group, and others.
It is important at least to implement this type of security on site, as often it is a user with unrestricted access which is working in the Enterprise view, where the Site Hierarchy is the initial panel that is displayed.
Adding the following overrides to a Security Profile which otherwise has no restriction will prevent accidental reparenting of Sites or Assets. The same types of relationships can be secured on other classes that may present a similar problem.
Here is an example of a profile that would secure against the ability to drag and drop Sites or Assets into alternate positions in their respective Hierarchies. Note that in the case of protecting Site movements, both Site and asset hierarchy relationships must be secured. Not doing this could cause the asset hierarchy to be out of synch with the site hierarchy.
In practice, if a security profile starts from a Read-only position, the ability to drag and drop would not be available, unless explicitly overriden.