Introduction

In ENOVIA, there are two major methods to control access to content, depending on the application you are using to create the content:

1. Baseline behavior
2. Direct access responsibility

In apps that use baseline behavior method, the ability to view, and work with an object is implicitly defined through a combination of:

• The collaborative space and organization membership of the user
• The maturity state of the object
• The content category of the object
• Possibly by inherited permissions from a parent object in a structure

In apps that use direct-access responsibility method, the ability to view, and work with an object is only determined by the responsibility assigned to the user.

Project Planning Access to Content

‘Project Planning’ app uses direct-access responsibilities, instead of baseline behavior responsibilities, to determine whether you can access a specific project, and whether you have permission to perform specific actions on it.

Any user with access to ‘Project Planning’ app can create a project.
The user who creates the project becomes the Owner of the Project and is automatically assigned the Leader responsibility for it.
Each project is accessible only by its Owner when it is created.

Adding Project Manager and Project Members with responsibilities

The Project Owner can add Project Manager and users as members of the project.
This is how you do it:

• Use the Members tab, in Project Planning app, to add users as members of the project, and to assign them responsibilities (Leader, Author, Viewer)

• Use the Members tab in the Project Information panel to define the Project Manager, who is automatically assigned the Leader responsibility.
  It is possible to have several Project Managers assigned to a project.
  The difference between Project Manager and a user with Leader responsibility is that
  Project Manager sees the project in "My projects" section from the home page whereas the Leader does not.

Responsibilities and Permissions

Each responsibility (Leader, Author, Viewer) defines a group of permissions for a project, including the ability to access it.

• Leader has all permissions on the project, including deletion.
• Author can modify all aspects of a project but cannot delete it. Author cannot add members.
• Viewer can only see the project and cannot modify it.

The following responsibilities and permissions are relevant for all object types in Project Planning app:

Note that you can assign a user who is not a project member to a project task. In this case, the user has access only to the task assigned to him/her and not to the whole project.

The following video illustrates the ‘Project Planner’ responsibilities and permissions as explained in this post: