Setup
How to give people access to Flourish Folio after installing it, and how to check that it works.
Overview
Folio builds reports over your own Salesforce data: tables, grouped summaries, cross-tabs and scorecards, with charts and exports. It runs entirely inside Salesforce. There are no settings to fill in, no credentials, and no callouts, so setup is a matter of permissions.
A report runs as the person looking at it. Folio reads your data with that person's own object, field and record access, so two people opening the same report can see different rows. The one exception is a report marked Run Elevated, which exists for public sites and is covered in Placing Reports.
Where Folio lives
The package ships three tabs, all reached from the App Launcher. There is no separate Folio app.
| Tab | What it is |
|---|---|
| Folio Reports | The front door. Every report as a card, and from a card the report itself and the Editor. |
| Folio Report Viewer | A bare viewer that shows one report, chosen by a link. See Links to a report. |
| Folio Definitions | The raw records behind each report. Each record page runs its report, with the record's fields beside it. |
Everything an admin does starts on Folio Reports.
Permission sets
One permission set ships with the package.
| Permission set | Give it to |
|---|---|
| Flourish Folio: Admin | People who build reports. Grants the three tabs, full access to report definitions, and everything the Editor needs. |
There is no permission set for people who only read reports. Most of them never need one of their own: they see reports where you place them, on a Lightning page, a Flow screen or an Experience site. What they do need is permission to run the viewer, and you grant it with a permission set you create:
- In Setup, create a permission set, for example Folio Report Readers.
- Under Apex Class Access, add
Folio_FormViewer. - Under Object Settings, give Folio Definitions Read, with read access to its fields.
- If they will use the Folio Report Viewer tab, set that tab to Visible.
- Assign it to the people who read reports.
That set lets someone open a report. It does not let them see data they otherwise could not: they still need read access to whatever the report is built on, such as Opportunities or Contacts, because the report reads it as them.
Report definitions are readable by everyone inside the org once they have object access, and private to outside users, so there is no sharing to set up for internal readers.
Checking it works
- Open Folio Reports from the App Launcher. If it is missing, the permission set is not assigned, or was assigned in this session: log out and back in, since tab visibility is read at login.
- Click + New Report, pick an object under Report On, and add a column. The preview should fill with rows from your org.
- Name the report in the header and click Save. The card appears on the gallery.
- Log in as someone holding only your reader permission set, and open a page where you placed the report. If the report does not load, check the Apex class access and the object permission in steps 2 and 3 above. Report not found or not accessible, on a report you know exists and is not archived, means the object permission is the one missing.