Skip to content
OrgGuard Docs

Reports & Dashboards Folder Access

Overview

Section titled “Overview”

OrgGuard ships two report/dashboard folders:

  • OrgGuard Reports — seven standard reports covering coverage, expiring certs, finding age, and ownership KPIs
  • OrgGuard Dashboards — ships empty in Pro 1.0. The folder is created and access-managed the same way, but contains no packaged dashboards yet. Build your own dashboards in this folder for now; packaged starter dashboards are planned for a future release. For at-a-glance coverage rollups, use the in-app Coverage tab.

After install, both folders default to org-wide internal user “View” access. Every internal user with the right Lightning app + permission-set assignment can view the folder’s contents. There is no group-based restriction out of the box — your subscriber admin shares the folders to whatever groups, roles, or specific users your governance program needs.

What you’ll see

Section titled “What you’ll see”

In Setup → search Folder Sharing (or open Reports → All Folders, find OrgGuard Reports, click the dropdown → Share). The folder-sharing dialog shows:

  • Public Group / Role / User dropdown — pick whichever sharing target you want
  • Access Level — Viewer (read), Editor (read + run + save modifications), Manager (read + run + save + share)
  • Currently shared to — the list of existing folder shares

The same dialog is available for OrgGuard Dashboards.

Common tasks

Section titled “Common tasks”

Task: Restrict access to a specific public group

Section titled “Task: Restrict access to a specific public group”

Use this when you only want a subset of internal users (your security team, compliance leads, etc.) to see OrgGuard’s reports and dashboards.

Who can do this: System Administrator, or anyone with the “Manage Reports in Public Folders” permission.

Prerequisites:

  1. Create the public group first if it doesn’t already exist: Setup → Public Groups → New, give it a name (e.g. OrgGuard Report Viewers), and add the users.
  2. Decide whether you want Viewer (read-only) or Editor (lets users save modified report runs into the folder).

Then:

  1. Open Setup → Reports → All Folders → OrgGuard Reports → ▼ → Share.
  2. In the dialog, set the type dropdown to Public Group.
  3. Type your group name; pick it.
  4. Set Access Level to Viewer.
  5. Click Add, then Done.
  6. Expected result: members of that group can read the OrgGuard Reports. Org-wide internal users still have View access unless you also set the folder’s default access to No Access (next task).
  7. Repeat for OrgGuard Dashboards.

Task: Lock down to group access only

Section titled “Task: Lock down to group access only”

Prerequisites: the group share is already in place per the previous task.

  1. Open Setup → Reports → All Folders → OrgGuard Reports → ▼ → Share.
  2. Find the org-wide entry (usually shown as Org-Wide Default: Viewer).
  3. Click the entry and change to No Access.
  4. Save.
  5. Expected result: only members of the public group(s) you shared to can read the folder. Subscribers without group membership get a “You don’t have access to this folder” message.

Task: Add another role or specific user

Section titled “Task: Add another role or specific user”

Same flow as Task 1, but pick Role or User in the type dropdown instead of Public Group. Useful for granting a single executive read access without creating a group.

Why this differs from earlier OrgGuard versions

Section titled “Why this differs from earlier OrgGuard versions”

Earlier pre-release builds of OrgGuard shipped a placeholder public group called OrgGuard_Report_Viewers that the report and dashboard folders were pre-shared to. AppExchange 2GP managed packages cannot ship Group metadata (every customer’s user/group structure is unique), so that fixture was removed. The folders now deploy with org-wide-internal default access; subscribers re-share to their own groups using the steps above.

Troubleshooting

Section titled “Troubleshooting”
SymptomLikely causeFix
User sees “You don’t have access to this folder”Org-wide default is No Access AND user isn’t in any shared group/roleAdd the user to a group that has View access, OR add a User-type share for that user
Reports run blank for some users but not othersFolder access is fine; the underlying objects (TrackedAsset__c, Finding__c, etc.) aren’t readable by that user’s profile/permsetAssign one of the OrgGuard permission sets — see Permission Sets
”Manager” user can’t share the folder furtherThey have only Viewer or Editor accessPromote to Manager via the folder Share dialog

FAQ

Section titled “FAQ”

Q: Can I share to a role hierarchy and have it cascade? Yes — share to a Role (with Subordinates option). Sub-role users inherit access.

Q: Will OrgGuard upgrades reset my folder shares? No. Folder share assignments live in the subscriber org and are not overwritten by package upgrades. Once you configure them, they persist.

Q: Can I delete the shipped folders entirely and use my own? Not recommended — OrgGuard’s standard reports are filed under those folder names; deleting them breaks the saved reports. If you want a different folder name, clone the reports into your own folder rather than renaming.

Q: Does my subscriber-side group config affect the underlying data security? No. Folder sharing controls who can open the folder. Object/field-level security (CRUD/FLS) controls what records and fields each user can see inside a report. Both layers must allow access for a user to actually see data.

Section titled “Related”