For specific instructions on how to perform these activities, see help available in the Participant Administration utility.
Registering a non-Windchill User
This procedure describes how to register a non-Windchill user. The registration can be done through an email notification when a non-Windchill user is added to project team. Perform the following:
1.Login as project creator.
2.Create a project.
3.Go to the Team page of the project and click the add participants to team icon
.
4.Under Email Invitation, add the non-Windchill user email ID (for example, abc@gmail.com).
The user for abc@gmail.com must open the email that is sent and click the Register action in the email.
To configure Windchill ProjectLink self registration, change the following properties in the <windchill>/conf/register/reg.properties file
# the ldap used: provider_url=ldap://pl-pla1.ptc.com:389
ldap://<LDAPserverName>.<MyCompany>.com:<port>
# the Directory Manager
principal=cn=Manager
# password for Directory Manager
credentials=wcadmin
# user_registration_subtree= to point to ou=people node in the LDAP
user_registration_subtree=ou=people,ou=pdmpjl,l= <location> ,o= <MyCompany>
Profile Management
Profiles allow the site and organization administrator to dynamically control which actions are visible to a user, group of users, or users in an organization by associating that information with a profile. A profile represents a typical category of user within a company and is based on the roles and privileges associated with that particular user category.
292 |
PTC Windchill® Basic Administration Guide |
By defining a profile that exposes only the necessary functionality and information needed by a user, it creates a focused and simplified user interface, reducing confusion by eliminating areas of the user interface that could be distracting. This capability allows customers to ensure that a supplier, customer, or group of users is presented with a streamlined and focused set of information and actions.
Each user or group can be associated with one or more profiles. The least restrictive settings for visibility are assumed. For example, if a user is associated with two profiles where one profile hides an action, but the other profile allows visibility of that action, then the user will see the action in the user interface. If one profile allows read only visibility to an attribute, but another profile gives full rights to that same attribute, then the user will have full rights to the attribute.
Changes that are made to profiles take effect after the user subsequently logs into the system.
Creating Profiles
Profiles are created from the Profiles sub-navigation link in either the Site
or the
Organization
contexts.
Users, groups, and organizations can be associated with a profile when creating or editing a profile from the Profile page. When creating a user from the Participant Administration utility, the user can be associated with any existing profile.
•The Profiles page on the Site context provides you, the site administrator, with access to all profiles created in the site context.
•The link from the Organization context provides access to only those profiles that are available through the organization context Profiles table as well as any profiles created in the current site context.
Profiles that are created in an organization context are peers to the profiles created in the site context, unless they are given identical names – that is, the system will merge the settings from all profiles that are associated with a user, regardless of whether they are defined at the site or the organization contexts in order to determine what will be visible to the user. When a profile is created in an organization context with an identical name to a profile created in the site context, the organization profile overrides the site profile.
For more information on creating a profile, see help available in the Participant Administration utility.
Profiles as a Visibility Control Mechanism
Profiles are not an access control mechanism; they are a user interface control mechanism.
Understanding Participants (Users, Groups, and Organizations) |
293 |
The profiles that are associated with a user, group, or an organization control which actions and areas of the user interface are visible by those users. A user could have permission to edit an object based on an object domain-based policy, but not have visibility to that edit action for the object because this action is not included in the user’s profile.
The primary goal in defining profiles is simply to hide the user interface elements (e.g., actions, tabs, and attributes) that a user has no need for or interest in. If a user does not have rights to an object or an action through access control rules, a profile will not add visibility to actions or information that are restricted by underlying access control policies. That is, you cannot grant a user visibility through a profile to an action or an area of the user interface for which that user does not already have access control rights. For example, a user could have access control permissions to the Create Part action in the system, but through a profile, that action can be hidden from the user and not visible in the user interface. On the other hand, if the user does not have access control permissions to the Create Part action, that action cannot be made visible to the user via a profile. It is the combination of a user being granted permission to an object or action via access control policies, and the profile granting visibility to those actions and objects, that will enable a user to see and perform an action.
When a profile is associated or disassociated from a user or group, no change in access permissions is implied or enforced.
Default Profile Behavior for a New User
When a user is added to the system and the user is not associated with a profile, the user will inherit the profile that is associated with the organization of which the user or group is a member. If the organization to which the user is added is not associated with a profile, and the user is not associated with a profile, then the user’s visibility to actions and areas of the user interface will be determined by the default profile system configuration. The user will not be associated with this default system profile but the system will use this profile for the user in the absence of any other profile association. For more information, see Global Default Settings on page 292 .
Global Default Settings
The out-of-the-box system default profile provides visibility to all functions and areas of the user interface. This system profile may be modified by the site or system administrator to provide visibility to a minimal number of actions and information elements.
A site or system administrator can globally configure the default visibility for actions as well as the standard out-of-the-box roles. This is done by modifying the out-of-the-box system default profile. For more information, see the PTC Windchill Customization Guide.
294 |
PTC Windchill® Basic Administration Guide |
Overriding Profiles in an Application Context
Profiles that are created in both the site and organization contexts can be overridden in a specific application context by the application context manager, such as in a specific project. For example, assume that a user is associated with a profile that is defined in the site context and this profile does not allow visibility to the actions that would allow that user to create folders in any application context. A project manager can override the site-defined profile privileges and allow visibility to the action for creating folders for that user within a specific project. Application context managers override the site-defined profiles from the Team page by using the Configure Actions for Roles option in the team in which the user is a member.
For more information on configuring the actions for roles, see help available in the
Participant Administration utility.
Default Visibility for Application Context Managers
The site and organization administrator can choose to set defaults for and hide visibility over a specific product, library, project, program, or other application context action or user interface element. That is, the site and organization administrator can carefully control which elements that application context managers (project, program, product, and library managers) are able to override in a context instance.
Removing the ability for an application context manager to override a profile setting is done by globally hiding visibility to the Configure Actions for Roles action for a specific context. If this is done, then the visibility of actions and areas of the user interface in a context instance cannot be modified by that application context manager.
If an action or user interface element is allowed to be configured or overridden by the application context manager in a context instance, then the user interface element will be displayed as a row in the Configure Actions for Roles table which is accessed from the context team’s Members table.
The site administrator can define a default value (to show or hide) the user interface element but if the user interface element is made configurable in a context, then the application context manager can override the default and choose to show or hide the user interface element per role in the context team.
Understanding Participants (Users, Groups, and Organizations) |
295 |