Configuring Visibility of Actions for Roles
From the Members By Role view and the Local Team Roles and Members view of the context team Members table, you can restrict the visibility of the actions in the user interface for the roles that are in the team.
 |
The ability to restrict the visibility of actions by role is not the same as restricting the visibility of actions for individual users, user-defined groups, or organizations. Restricting visibility for individual users, groups, or organizations is done through the use of profiles. For information on profiles, see Managing Standard Profiles.
|
You can indicate which set of actions should not be visible to those members of the team who are in selected roles. The visibility is not controlled by access control rules and is not contingent on certain permissions being set. Configuring actions for roles determines what appears in the user interface when users are in a specific team role and are accessing the context in which the visibility has been restricted.
|
|
Only context managers, organization administrators, and site administrators can configure the visibility of an action for a local team from the Members table that displays the local team roles and members. You cannot configure the visibility of an action for a shared team.
|
Use the following steps to remove the visibility of a set of actions for members in a specific set of roles:
1. Click the configure actions for roles icon 
on the Members table.
on the Members table.The Configure Actions for Roles window opens.
 | You can reduce the number of roles that display by selecting the checkbox next to the roles to configure before clicking the configure actions for roles icon . |
2. Select or clear the actions in the Configure Actions for Roles window as appropriate for each role.
When determining which actions to hide, consider how some of the actions work together. For example, the Cut, Copy, and Paste actions work together. If you hide the Cut and Copy actions, you should also hide the Paste action.
Also consider how some actions require the visibility of other actions. For example, to modify a team, you must be able to view the Team page. Therefore, do not hide the View Team Page action for those roles where the Modify Team action is visible.
| | Some actions are restricted and do not appear as selectable for all roles. For example, the Edit Access Control action is not an action that you can make visible for members in the Guest role. |
Additionally, some actions for the context manager are always visible and cannot be changed. For example, the action to view the Team page is always visible for the context manager.
3. Click OK.
The selected actions are visible to the members assigned to the selected roles according to your settings.
| | If you select roles to be configured, rather than configuring all roles, the Team Members column is always shown and changes based on your settings. This column represents the settings for the Team Members group and the settings saved for this group are used for any roles that you add in the future. |
For those roles that have not been specifically configured, Windchill saves the default configuration for each role. The default configuration is the configuration that is displayed when you initially display the role in the Configure Actions for Roles window (before making any changes).
| | After configured, the actions for roles can be carried over to a new application context using the Save As action in the context. |
For information on how using the configure actions for roles icon affects the use of profiles, see Using Profiles and Action Visibility for Roles.
affects the use of profiles, see Using Profiles and Action Visibility for Roles.If you have configured some roles to restrict the visibility of some of the actions, you can include those visibility restrictions when you export the application context, save the context as a template, or save as a new context. To include the restrictions, be sure to select team roles when exporting, saving as a template, or saving as a new context. For details on exporting or saving a project as a template, see Methods of Creating Additional Context Templates.