Axeda applications provide four customizable privileges (Custom Privilege 1 – 4) that can be used by custom object developers to restrict user access to their custom functionality. The actual functionality limited by the custom privilege is defined by the custom object developer. Note that although all four custom privileges appear in the Platform, not all may be implemented for custom objects.
When developing your custom object, you can limit user access based on specified privileges. Your custom object can use the API packages com.axeda.drm.sdk.privilege and com.axeda.drm.sdk.user to apply privileges, including custom privileges, to custom object functionality.
For a typical implementation, all users associated with user groups that are defined with “Custom Privilege 1” will be able to use the functionality defined by that privilege.
Note: Make sure you explain how your custom objects work and which privileges are required for those objects.