Industrial Automation
Industrial Automation | Europe

myKnowledge

Main > Product Type > Automation Systems > HMI > NA
Minimize Text   Default    Enlarge Text
 

Print
E-mail

Introduction To Security In The NA


Overview


The security settings can be found within the Configuration and Settings area of the solution explorer. Double clicking on ‘Security’ loads the settings page. The security settings are divided into three main areas:

 

Users

New users can be configured, passwords set and roles assigned.  Up to 50 users can be defined.

Roles & Access Levels

In this area the roles and levels are configured in a kind of matrix.  Up 20 roles and 20 levels can be defined and both roles and levels can be renamed to meaningful names.

Security settings

In v1.0 the other settings include an auto log out following inactivity and a system menu level.

 

 

Users

By default an ‘Administrator’ user is always included in an NA project with the password of ‘administrator’. It is possible (and even recommended) to rename this user and change the password. It is even possible to remove this user, but only if further users have been defined. To add a user simply click the ‘+’ button. To delete a user click the bin icon next to the ‘+’. A user name can contain up to 40 characters. A password must be defined for each user, which has to be between eight and thirty-two characters (same rules as the NJ). A comment can be defined to better describe the purpose of this user. A role must be selected for each user (see below on configuring roles & levels)

Roles and Access Levels

Roles and Levels are configured in a matrix. Each level is distinct – that is to say that if a user has Level 2, he does not automatically have Level 1. Both columns would have to be selected in the Role.
It is not possible to rename or delete the Administrator Role.

 

 

It is possible to add up to 20 Roles and 20 Levels. When assigning these roles to users, bear in mind that when these settings are applied to objects there are two settings: Accessibility Level, and Visibility Level. That is to say that it is possible to configure it so that some users can see some
buttons/lamps etc but cannot access them, whereas some users may not even see those buttons/lamps on a page.


In the example shown above, having set the access up as a triangle, it is possible to treat the levels as a hierarchy – but again actually they are all distinct levels.


For more information about how to use Security on Pages please refer to Getting Started with Security in NA’ article
 

See Also:

Introduction to the NA series HMI




Comments (View All Comments / Add Comment)

Related Articles
No related articles found.
Created 2014-06-30
Modified 2015-04-08
Views 5112

 

You are not logged in.