Skip to main content
Share / Export

Configuring VA Report Security

VA Report Security sets who can run reports when they may show confidential data. Filter in the header, then set access by security group or user. After the grid is filtered, either initialize the same settings to all rows or assign each group/user. Denied reports gray out in the module Reports folder and are inaccessible. Users can hide those with Main Menu View → Display Accessible Items Only.

Trimble form: VA Report Security Form. Procedures under Apply Report Security Settings.

Before you start​

  • Read About the Interaction Between Group and User Level Security Settings.
  • Optional: review RP Report Titles; if a layout changed, run RP Report Layout first so RPRF (Report Objects) is updated.
  • If VA Security Administration is on, you may only apply security for some company/module combinations, and the grid may show only those regardless of Modules selected.
  • SSRS security applies only if Sync Security is checked in RP RS Server.
  • You must already have form security to administer report security for the companies/Global you use.

Filter the grid​

  1. Set Companies — one, many, or Global (all companies, including companies added later). Missing company or missing Global usually means no form-security permission for that company or for all companies.
  2. Set Modules — or All.
  3. Set Select By: Group # (numeric), Group Name (alpha), User, or Report (report list also depends on Modules).
  4. Use the Groups/Users/Reports picker. Search is case-sensitive. Typing a first character checks the next match. All selects only the current search results, not items the search hid.
  5. Click Refresh Grid. Hierarchy: Report = Company, Module, Report, Groups/Users; Group # or Group Name = Company, Module, Group, Report; User = Company, Module, User, Report. Grouping checkbox plus drag column headers changes display. Refresh Grid again clears the grid.

Initialize (same level for every row)​

  1. Filter, Refresh Grid (enables Initialize Access Level).
  2. Click Initialize Access Level. Warning: it changes all records in the grid, not only visible rows. Re-initialize overwrites prior individual changes.
  3. On Initialize Security Access, pick Access Level → Apply. Grid then shows that level and record permissions.
  4. Optionally tweak specific rows (manual path), then Apply to save. Optional second Refresh Grid clears the grid.

Manual assign​

  1. Filter. Expand the hierarchy.
  2. Per row, set the Access column dropdown.
  3. Apply → success message and group/user security updates. Optional Refresh Grid to clear.
  4. A later initialize replaces individual changes.

Hard rules​

  • SSRS: always use Global. SSRS security does nothing unless RP RS Server Sync Security is on. Field defs say any user with SSRS access in one company can run it for all companies; Filtering/Manual also say grant access in all applicable companies for cross-company runs.
  • Global access covers future companies.
  • Initialize is grid-wide, including rows not visible.
  • Deny grays the report icon; users toggle visibility themselves.
  • Prefer global/group settings unless you have a clear reason for company- or user-specific report security.

Notes​

  • Related: VA Security Administration; About the Interaction Between Group and User Level Security Settings; VA Security Groups; View the Audit Log; Initialize Security Access; RP Report Titles; RP Reports by Form; RP Reports by Module; RP Report Type; Associating a Report with a Module; Adding Reports to Module Menus; RP Report Layout; Sync Security / RP RS Server; SSRS Overview; User Permission Levels; VA Form Security.