You are here:
Fundraising Editions and Permissions in Nonprofit
Review the supported products and editions for Fundraising. Then check out how your product handles permissions and how to assign them.
Required Fundraising Permissions
To use Fundraising, Salesforce admins and users need the user permission Fundraising User. Typically, a Salesforce admin assigns a permission set or permission set group, which includes this user permission.
| Product | Permission Set or Permission Set Group | Notes |
|---|---|---|
| Nonprofit Cloud | FundraisingAccess permission set | This permission set gives access to the Fundraising permission set license, user permissions, and all objects and fields. |
| Nonprofit Cloud | Fundraising_User permission set group | Assign this permission set group to people who use Fundraising features. Provides access to all Fundraising features and related pages. Some features require enablement. |
| Nonprofit Cloud | Fundraising_Admin permission set group | Assign this permission set group to Salesforce admins who set up and configure Fundraising. Provides access to all Fundraising features and related pages, plus permission sets to configure Data Processing Engine and Omnistudio. |
| Nonprofit Cloud | FundraisingExperienceCloud | Assign this permission set to give Experience Cloud users access to select Fundraising objects and components. |
Customizing Permissions
If you customize this feature, such as adding fields, create a custom permission set. To remove user permissions from the default permission set, create a muting permission set. Then, use permission set groups to assign users the default permission set in addition to your custom permission sets and muting permission set. This approach makes sure that users always have the latest default permissions and is an alternative to cloning permission sets.
SEE ALSO:
