To see the Folderize, Community users must have access to the app’s pages, objects and etc.
The installed package includes ready permission sets that simplify configuration of access to Folderize features.
Most commonly, you would want to grant Community users read-only permission on your document collection. To achieve this, you can assign to them either of these Folderize permission sets:
- SMF Read-Only User;
- SMF Object-Record View: Read-Only User, if using object-record mode.
A Permission Set can be assigned manually or automatically via a custom APEX-based solution (e.g., via APEX trigger).
In theory, you may decide to grant more permissions, e.g., allow uploading by Community users. But it needs to be done carefully to avoid inadvertently granting overly broad privileges to external users. If needed, ShareMethods, publisher of Folderize, offers the option of a short consulting engagement to help configure Folderize for a Community according to your needs. If you might be interested in this, please submit the questionnaire.
For Salesforce Sites, instead of a permission set, use the site profile (public access settings) for app permissions. See the Profile Settings page for the read-only settings.
An Aside About Salesforce Licenses
Folderize stores its documents in the Salesforce Files object. Thus Community users need a Salesforce license allowing access to Files. (But note that Folderize will work with the Files tab hidden.)
If you find that Folderize users cannot see documents, despite enabling the settings discussed below, here is a way to check if licenses are the issue: Temporarily add the Files tab to the Community, and share a file with Community users. Then login as a user and confirm that they see the Files tab and any document. If not, you may need to talk with a Salesforce sales representative about enabling Files for your Community users.
Folderize User Guide and Administration 