Working with Project-based Security

Propagate Security

When saving a CATIA structure to SmarTeam, you may select both Secured By and Propagate Security for the selected project. If the user permissions do not allow setting Secured by project for some components in the structure, the Save operation will be completed but the Secured by project setting will not be applied for these components.

A warning message appears, displaying a list of the objects to which the security was not applied.

Switch to Latest Revision with Permissions

When working with Project-based Security, assembly components are attached to projects whose security context is defined through roles. In some cases, when you modify the top-level assembly, you may not have sufficient permissions to view or modify the latest revision of certain assembly components. When Always checkout or new release latest available revision is selected, or when the user selects Switch to latest, SmarTeam checks the permission definitions for all revisions of the components, and provides access to the latest revision for which the user has the required permissions.

The LifeCycle and File Operations Report dialog box displays the following notification:

• When a component is switched to a revision that is not the latest:

Warning No. 31816 Current user have no permissions for PRT-0000306 a.4 New Text Document (3) Checked In Object switched to PRT-0000306 a.1 New Text Document (3) Checked In.

• When the user does not have permissions for one or more objects in the structure:

Warning No. 31817 Current user have no permissions for one or more objects in this structure.

To enable this functionality, the SmarTeam Administrator must set the LifeCycleSetUp.ConsiderPermissionsForSwitchToLatest key on the Domain level to YES using SmarTeam System Configuration Editor.