Managing access rights for a database-based industry model

The Security Administrator defines user roles with user-defined access rights for a database-based industry model. These access rights can be divided into “Read”, “Insert”, “Update” and “Delete” and can be separately defined for each table.

Example

mceclip0.png

 

Creating a role

Open the Security Administrator. 

mceclip1.png

Then click on “Add role”. 

mceclip2.png

For example, create a read-only role (in this case: NET_DEMO_WS[xx]_RO)

mceclip3.png

  1. Role name (corresponds externally to the document name)
  2. This defines which rights are used to access which main document.
  3. “Save” creates the role.

Editing a role

Open the Security Administrator as described above. 

Select the role to be edited and click on “Edit”. 

 mceclip4.png

In the edit mode, the table-specific rights of a role can be adjusted afterwards. The following settings are available:

Right

Meaning

Select

Objects can be selected and read

Add

New features can be created

Update

Existing features can be modified

Delete

Existing features can be deleted

Run

Functions/packages can be run

Modify

Sequences can be modified

Direct

Direct access (necessary for writing PL/SQL code)

 

For example, allow updating for the table TC_TG_BUILDING and “save” the change. 

mceclip5.png

Finally, assign the document you have just created to your enterprise project