Definition of Permissions

 

 

 

Links/ Videos:

 

Below, the different permissions that can be Granted or Denied. By default, they are inherited from the nearest parent. For example, if the project grants a user to export or print, this user will be able to export or print from a subfolder or a document of the project. If a folder forbids it explicitly, documents of the folder will not be exported or printed.

 

Available permissions:

 

 

A user with administration rights will not be able to manage other users. You must be logged as "Admin".

 

 

Administrate

 

Allows to define the security of the project, the folder or the document

Create

Allows to create in a project, a folder or a document. Read authorization is also required to open it as read only mode and/or Modify authorization to be able to change properties or to modify geometries.

Read

Allows to open in read only mode and to see the contents of a project, a folder or a document. It will not be possible to modify it.

Modify

Allows to modify properties of the project, the name of a folder or to modify a document.

Modify References

Allows to add or remove references from the project.

Export / Print

Allows to export a package or to print a document. If one of the folders or documents does not authorize the export, the project cannot be exported. If the project or a folder does not authorize the print, it will not be possible to print documents of the project/folder.

Delete

Allows to delete a project, a folder or  a document. If one of the folders or documents does not authorize the deletion, the project cannot be deleted.

Life cycle state change

Allows to indirectly change the life cycle state by validating for example the life cycle of a draft which references the project. It is not possible to directly change the life cycle state of a project. To change the life cycle state of a document, it must be checked in.

Publish to Plm

Allows to publish to Plm a project (If all its contain is validated) or a document. If one of the folders or documents does not authorize to publish or is not checked in, the project cannot be published.

 

 

  • If a user is defined in several user groups with different rights, the most restrictive rights will be applied.

  • The Inherit information indicates that the security comes from the direct parent. For example, if an authorization is given to the project, all folders and documents are modified to take into account this authorization.

 

 

Some permissions depend on others. They are checked together:

  • To create, you must be able to modify and read. By granting Create, the 2 others are also granted.

  • To modify, you must be able to read. By granting Modify, Read is also granted.