Scientific Notebook Roles and Access Rights

The 3DEXPERIENCE platform is a collaborative environment for managing your business processes based on defined roles that provide secure access to content.

This page discusses:

Content Categories

Depending on your access role, you can create and manage the following types of content with Scientific Notebook.

Content Type Description
Experiment All users with at least the Reader role for an experiment can access all of its content.

Access to an experiment is also controlled by through its project.

If you have create or read rights for a project, you can view all experiments in the project.

If you have create rights for a project, you can create experiments in the project.

For more information, see Projects and Managing Projects.
Experiment Type Only users with the 3DEXPERIENCE Platform Administrator role can create and manage this content.
Project Only users with the 3DEXPERIENCE Platform Administrator role can create and manage this content.

The Scientific Notebook content you can access and the tasks you can perform depend on your access role. For imported experiments, you cannot edit access roles, users can access:

  • Experiments that they submitted using BIOVIA Notebook.
  • Experiments that they checked in using BIOVIA Workbook.

Access Roles for Experiments

Scientific Notebook uses the access roles assigned to you by the Owner of an experiment or a user with the 3DEXPERIENCE Platform Administrator role. The table below describes the level of access.

Access Role Description
Reader Users can read experiments for which they have this access role.
Collaborator Users can read and modify experiments for which they have this access role.
Owner Users can configure all aspects of an experiment.

Users can share the experiment with any other Scientific Notebook user, even if they do not have access to the experiment's project.
3DEXPERIENCE Platform Administrator Users can configure experiment types and projects.

For all access roles, an experiment Owner or a user with the 3DEXPERIENCE Platform Administrator role can assign the additional Reviewer access role to individual users of each Scientific Notebook experiment. The Reviewer access role controls users' ability to transition experiments in their lifecycles.

Primary Access Role Additional Access Role Description
Reader Reviewer Can transition an experiment in the Pending Review lifecycle state or in Completed.
Collaborator Reviewer Can transition an experiment in the Pending Review lifecycle state or in Completed.
Owner Reviewer Can transition an experiment between any lifecycle states.

Access Rights for Projects

Scientific Notebook uses the project access rights assigned to you by a user with the 3DEXPERIENCE Platform Administrator role. The table below describes the level of access.

Access Rights Description
Read Users can read all experiments in the project.
Create Users can create experiments in the project and read all experiments in the project.

All Access Roles

The access roles provide hierarchical access. For example, an Owner includes all access that a Collaborator has (who has all access that a Reader has), plus additional specific accesses. In the above tables, an access role has all the accesses of the roles that appear above it.

You can assign access roles to individual users or to user groups, defined in the User Groups app. For more information, see User Groups. If a user has different roles individually and from user groups, they have access to all actions from all their roles.

Your business administrator can configure rules that change the default access behavior.

On premises only: Your business administrator can change the default responsibilities that control your access to commands, content, and collaborative spaces. Companies can also implement additional customized responsibilities.

This guide describes the default behavior when describing access to content or commands.

Your access role determines your access to content or commands in Scientific Notebook. Your organization, the current lifecycle state of the content, the app you are using, and other custom access controls all affect whether you can access content or commands. You might have access to some content or commands only under certain conditions.