Roles

The role determines the functions that the user is authorized to perform, such as viewing or modifying data.

One of the important tasks of the administrator is to create and define roles, and associate the roles with relevant users and relevant projects. When a user is linked to a project, it is also required to specify the user role in the project. Various PLM actions are linked to roles. Permissions and access to objects must be specified during the definition of the role.

During PLM Implementation, it is recommended to revise the predefined roles and make sure that the permissions are defined according to the requirement of your organization. If more roles are required, it is important to choose an existing role that is similar to the required role and use it as a basis template for the new role.

The Roles (pdadm4601m000) session is used to define new roles, update existing roles for appropriate authorizations and delete roles that are not required.

Note: Only the roles that are not assigned to a user can be deleted.

By default, these roles are available. These predefined roles cannot be modified. If you want to modify a role, you must copy the role and modify the copied role.

  • General Administrator
  • Design Engineer
  • Project Administrator
  • Project Manager
  • Observer
  • None

Define Objects by roles

The basic data components of the PLM system are referred to as objects. Examples of object types are documents and items, and system administration objects such as, projects and users. The various PLM objects are linked to roles and access to these objects are defined while defining the role. An administrator can create a new object, associate the object to a role, sort objects, group objects, and navigate through the objects.

Note: The actions specified for an object can be allowed or overridden by a particular role.