Definition Of Roles - HEIDENHAIN TNC 620 User Manual

HEROS functions | User administration

Definition of roles

HEIDENHAIN combines several rights for individual task areas to
roles. Different pre-defined roles that you can use to assign rights
to your users are available. The tables below describe the individual
rights of the different roles.
Every user should have at least one role from the
operating system area and at least one role from the
programming area.
You can enable a role either for local login or for remote
login. With local login, the user directly logs on to the
control at the control's screen. A remote login (DNC) is a
connection via SSH.
You can therefore also make the rights of a user
dependent on the access he uses to operate the
control.
If a role is only enabled for local login, Local. is added
to the role name, e.g. Local.HEROS.Admin instead of
HEROS.Admin.
If a role is only enabled for remote login, Remote. is
added to the role name, e.g. Remote.HEROS.Admin
instead of HEROS.Admin.
Further information:
Page 410
Advantages of classification in roles:
Easier administration for the end user
Different rights are compatible between different software
versions of the control and different machine manufacturers.
Various applications require access to certain interfaces.
Where required,the administrator also needs to set up
rights to access the required interfaces as well as rights
to access certain functions and additional programs.
These rights are granted by the operating system roles.
The following contents can change in the following
software versions of the control:
HEROS role names
Unix groups
Basic ID number
HEIDENHAIN | TNC 620 | User's Manual for Setup, Testing and Running NC Programs | 10/2018
"Creating further users",
10
415