|
<< Click to Display Table of Contents >> Navigation: Revisions > Revisions security |
MechworksPDM assigns two levels of security to its operations:
1.Simple DBWorks Users operation
2.DBWorks manager operation
By default, every user is a DBWorks manager, so he can perform every operation on MechworksPDM.
MechworksPDM creates, under Windows NT, a local group named DBWorks Users; if a user is assigned to this group, he becomes a Simple DBWorks User, and cannot have access to the following operations:
1.Creation, approval or freezing of revisions
2.Creation, reassignment, deletion of projects
For the Standalone version ( that is running on workstations without the 3D CAD installed ) , there is also another level of security, controlled by the belonging to the group DBWorks Standalone Power Users.
If registered in it, the user can modify the database by opening it with the 'Open for update', can edit the data of any single record, can execute scripts that modify the database.
If not registered in the group ( default case ), the user can basically only VIEW the records, build BOM output and TREE outputs, but cannot in any way delete data.
This group is also automatically created by MechworksPDM the first time it executes and can be viewed with the standard Administrative Tools, User manager functionality of Windows NT. As specified earlier, it is the responsibility of the administrator of the network to assign or not to assign the users to this group.
When two different users on a network try to modify the same part, there are two elements to be taken into consideration: who checked out the part first and their hierarchical levels.
Currently only two hierarchical levels are implemented: Administrator and User. By Default, after the installation, you are granted Administrator privileges.
The Administrator controls and manages the project deciding if and when a revision can be approved and hence released. He also decides if any changes brought to the part during a check out are to be discarded or accepted for a new check in during a work in progress.
On the opposite a User can only check out a part previously checked in, bring modifications and eventually check it in again. He cannot create a new revision nor approve it for release.
While a User has checked out a part for modifying it nobody else can, neither another User nor the Administrator.
After the User checked in a part after modifying it, the modifications can be rejected by the Administrator who could decide to undo the check in.
More information on the security issue in general can be found at the topic Security.