Security permissions: work with alarm history databases

Use the following table to determine which security permissions are required to work with alarm history databases.
To read from and write to the specific databases that contain alarm and event data, you must know the user name and password associated with the database. You enter this information as part of setting up a database definition.
To do this
Explorer window object
You need these permissions
Work with database definitions
Connections > Databases folder
Common > List Children
Common > Read
Add a new database definition
Connections > Databases folder
Common > Create Children
Common > List Children
Common > Read
Common > Write
Edit a database definition
Connections > Databases folder
Common > List Children
Common > Read
Common > Write
Delete a database definition
Connections > Databases folder
Common > List Children
Common > Read
Common > Delete
Common > Write
1
If Common > Read is denied for the Connections folder, the folder is not visible from the Explorer window.
If Common > List Children is denied for the Connections folder, Databases folders are not visible.
If Common > Write is denied for the Connections folder, the database definition properties cannot be changed.
1
Common > Write permission is required to delete a database definition only if you also want to unregister the alarm servers that are using the database definition.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal