As of 6/7/2023 this feature is no longer available. This article is for legacy documentation only.
Before You Begin:
- You need staff permissions to edit Info Hub settings and to edit access levels.
- Know which reports the contact needs to run, so you can grant View access for the matching modules. For example, if someone needs to run a Contacts Report via the Info Hub, the access level must include View permissions for the Contacts module.
- Have the access level you want to grant reports access to ready to edit.
Step-by-Step Instructions: Enabling Show Reports in the Hub
- Click Settings in the left-hand rail.
- Go to Memberships, Info Hub section, click Settings.
-
Scroll down to the Other Options section and enable the Show Reports in the Hub option.
- Click Save.
This will enable the display of the reports from GrowthZone in the Info Hub to anyone with 'View' or higher permissions for Reports in their access level.
Verifying Module Access for Info Hub Reports
We also need to verify/enable access to the necessary GrowthZone modules for the contact, depending on which reports they may be allowed to run. This module-level access will allow contacts to run the reports they are allowed based on the module access given.
-
In the access level in which you are granting the reports access, enable the Show All Areas option at the bottom of the window.
-
This will display the back-office module access levels. Set any necessary module access levels to View. For this example, our contact needs to run Contact Reports and Event Reports; they will need View access in both these modules.
- Make changes/adjustments as needed and click Done.
| Best Practice: Set any/all System Default levels to either "None" or "View" and grant access to each area explicitly as needed. |
In this way you can "silo" information access by creating specific access levels for specific reports in the Info Hub.
Common Pitfalls
- Enabling the Hub option but forgetting module access: Turning on Show Reports in the Hub alone is not enough — each contact also needs View (or higher) access to both Reports and to the specific module the report draws from, or the report will not appear for them.