Permissions
- Last UpdatedJul 05, 2024
- 1 minute read
AVEVA Enterprise SCADA stores all Permissions as Active Directory Application Mode (ADAM) Groups and these are typically not modified for your use. These groups do not appear within Active Directory (AD). During configuration, AVEVA Enterprise SCADA associates with the DNA Permission Groups to provide controls within the user-level applications.
These groups should not be deleted as it will impact the stability of the AVEVA Enterprise SCADA system. Users are not typically granted membership directly in DNA Permission groups. Instead, DNA Authorities are made members of the DNA Permissions, and users are a member of specific DNA Authorities.
DNA Permissions should be treated as capabilities, while DNA Authorities should be seen as specific roles or jobs within the AVEVA Enterprise SCADA environment.
Note: Membership information for DNA Permissions is based on the default configuration. Membership is not restricted to the groups indicated and may include customer-created DNA Authorities, however the groups shown are rarely removed from their default DNA Permissions.
Related Links
- DNA Permission — Change_Shift
- DNA Permission — Config_Database
- DNA Permission — Config_Displays
- DNA Permission — Config_OASyS_DNA
- DNA Permission — Control_SCADA
- DNA Permission — Critical_Alarms
- DNA Permission — Exit_XOS
- DNA Permission — MoC_Administer_Changeset
- DNA Permission — MoC _Administer_Emergency_Package
- DNA Permission — MoC_Administer_Package
- DNA Permission — MoC_Audit
- DNA Permission — Modify_XIS_Data
- DNA Permission — Schedule_Ops
- DNA Permission — Security_Administration
- DNA Permission — Supervise_SCADA
- DNA Permission — System_Administration
- DNA Permission — View
- DNA Permission — View_Alarms
- DNA Permission — View_Diagnostics
- DNA Permission — View_Security
- DNA Permission — View_System
- DNA Permission — XIS_Archive_Ops