Rights/access Control

<< Click to Display Table of Contents >>

Administration > Roles >

Rights/access Control

Background

The following is an instruction for how the flow works when building roles and giving permissions to different users in dpSpatial.

Users of Digpro's products can edit and create roles according to their own wishes and needs. In order to better understand how to use access control in the products, there are some basic facts that the user needs to take into consideration:

For customers that started using the product after version 7.2 the access control in dpSpatial follows the following structure:

oRoles in the Base platform - Application-independent standard roles (See User roles - standard roles for more information)

oRoles in the Application - Application-specific standard roles (See User roles - Product/ module-specific standard roles for more information)

o                           - Customized additional roles

 

For customers that started using the product before version 7.2 the access control in dpSpatial follows the following structure:

oRoles in the Base platform - Application-independent standard roles (See User roles - standard roles for more information)

oRoles in the Application -  Customized standard roles

o                             -  Customized additional roles

 

Roles in the Base platform - application-independent standard roles are roles that looks the same for all customers. These are uneditable and cannot be handled by the individual user of dpSpatial but are standard roles that are always included when installing with new customers. The basis for role and access building in the applications.

Roles in the Application - application-specific standard roles are roles that looks the same to all customers. These are editable roles, that can be handles by customers with administration rights in dpSpatial.These roles are viewed and handled in the User manager. Depending on which applications that is installed, the users will be assigned Application-specific standard roles. These standard roles for the application will be assigned to the users by default upon installation.  Example: For customers installing dpPower the roles starting with "EL" will be assigned. For thhose customers installing dpCom the roles starting with OPTO will be assigned to the users.

Roles in the Application - Customized standard roles are also application-specific standard roles. They have standard rights but may vary by name from company to company. Therefore, they are called customized standard roles. These roles are editable by customers with administrations rights in dpSpatial and are viewed and handled in the user manager. Depending on which application or applications are installed, these application-specific but customized roles may look a little different. For example, ELXXXREAD or XXXREAD where XXX is the customer-specific abbreviation.

Roles in the Application - Customized additional roles are roles that does not follow any Digpro standard regarding roles. Instead these roles are customized according to the company's own needs.

 

See which standard roles are available in the role descriptions in the following sections. There is a list of application-independent standard roles (Standard roles and Database roles) as well as the application-specific roles. For information about customized roles, contact your Customer support or Digpro support.

 

Modules

For each application there are modules. Example of modules are Operator, Designer, and Maintainer. These modules are controlled by module specific roles and features and can be configured by Digpro upon request.

 

The Rights editor

The Rights editor handle each users access to read and write in dpSpatial. Example: The PD_ACCESS roles for each module and application control which fields containing personal information that is visible for the user in dpSpatial. Fields being hidden for users not having the PD_ACCESS role are fields that contain information classified as personal information. For example the field Customer/Customer facility.

 

What can be controlled, or not be controlled

What can be controlled is for example access to the administration menu in dpSpatial. The administration menu is controlled by an administration role. This role can only be handled by the system administrator at each company.

What cannot be controlled are functions that need configuration by Digpro, such as role control of menu options.