Configure PI Server security
- Last UpdatedFeb 09, 2026
- 1 minute read
- PI System
- RtReports 5.1
- Visualization
PI Servers can be added in the same way as PI AF servers. Use the table below when configuring each PI Server you plan to access through RtReports.
RtReports Server (to PI Server)
|
Database Security |
Permission |
Notes |
|---|---|---|
|
PIBatch |
r |
|
|
PIDBSEC |
r |
|
|
PIModules |
r,w |
RtReports creates and writes to PI modules for application data (by default, under \%OSI\RtReports) |
|
PIMSGSS |
r,w |
r,w: to write to the PI Server message log |
|
PIPOINT |
r,w |
r: in RtReports Server 3.1.1 and prior r,w: in 3.2 and later, RtReports creates tags to store report comments |
|
Point Database |
Permission |
Notes |
|---|---|---|
|
PtSecurity |
r,w |
r: in RtReports Server 3.1.1 and prior r,w: in 3.2 and later, RtReports maintains tags to store report comments |
|
DataSecurity |
r,w |
r: in RtReports Server 3.1.1 and prior r,w: in 3.2 and later, RtReports annotates tags to store report comments |
|
Module Database |
Permission |
Notes |
|---|---|---|
|
Module Security* |
r |
No access required for new RtReports 5.1 installations or upgrades to RtReports 5.1 that have migrated application data to AF. r,w: required for RtReports 5.0 and earlier, and upgrades that have chosen to continue to store app data in MDB. The \%OSI\RtReports node of the MDB is to read or write application data (report templates, RtReports app-level security) |