You can use person, group, role, association, policy, and rule
administrative objects to control user access. In certain circumstances, users can grant
access to other users. When multiple types of access are defined, you need to know which
accesses take precedence over others.
Access means controlling the
information users see and the tasks they can perform. When users attempt to perform
tasks on a business object, they can only perform the task if they have been assigned
access. For example, viewing a file checked into the object or changing the value of an
attribute for the object. To see a list and descriptions of the accesses you can assign
and deny, see Access Privileges.
When working with an application that has a user interface external to the 3DEXPERIENCE Platform, you can control who sees various components of the user interface, such as
determining who sees specific pages and links on the pages a custom applet. If the
application is built with configurable component objects, you can use access features of
those components to control access. For more information about configurable components,
see the Legacy ENOVIA Web Apps
Customization Guide.