You are here:
Program Management Editions and Permissions
Review the supported products and editions for Program Management. Then learn about how your product handles permissions and how to assign them.
Required Editions
| Available in: Lightning Experience |
| Education Cloud: Enterprise, Performance, Unlimited, and Developer Editions |
| Nonprofit Cloud: Enterprise, Unlimited, and Developer Editions |
| Public Sector Solutions: Enterprise, Performance, Unlimited, and Developer Editions |
| Net Zero Cloud: Enterprise, Performance, Unlimited, and Developer Editions with Net Zero Cloud Growth |
Required Permissions
We recommend that you use permission set groups and muting permission sets to manage user access. To see what’s included in a permission set, click View Summary on the permission set’s detail page in Setup. Review your cloud’s documentation, too.
| Permission Set Name | Notes |
|---|---|
Advanced Program Management OR Education Cloud Full Access |
Assign to all users who work with Program and Case Management. This permission set includes user permission, permission set license, and object access for benefits, cases, cohorts, complaints, goals, programs, and recurring schedules. |
Net Zero Cloud Admin OR Net Zero Cloud Manager |
Assign to all Net Zero cloud users who work with Program and Case Management. This permission set includes user permission and object access for programs and initiatives. |
| Program and Case Management for Experience Cloud | Assign to all users who access Program and Case Management features on an Experience Cloud site. |
Program Management Guest Access |
Assign to the Guest User profile and include Program, Benefit, Benefit Type, Benefit Schedule, Benefit Session, and Referral object sharing for unauthenticated users to browse programs and benefits on an Experience Cloud site. |
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.
