--- schema_version: "1" id: 6865e1ed514fa621aee6934f35f90ce24964c957c6920f6a45a6fa83abc18724 title: Permission Sets collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/sfdo/264-0-0/pmm_configure_permission_sets.md canonical_url: https://help.salesforce.com/s/articleView?id=sfdo.pmm_configure_permission_sets.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: f10d16338ab2b4cad628de2a10490ebc432cf57bf08e2518e3fa1975a628ad41 description: Assign Program Management Module permission sets to give users the right level of access and keep your data secure. products: - Nonprofit release: "264" --- # Permission Sets Assign Program Management Module permission sets to give users the right level of access and keep your data secure. - **[Program Management Module Permission Sets](https://help.salesforce.com/s/articleView?id=sfdo.pmm_configure_permission_sets.htm&release=264.0.0&type=5)** A user only needs one Program Management Module permission set; however, it can be combined with other product permission sets as needed. Users can have only one profile, but they can have multiple permission sets. - **[Assign Permission Sets](https://help.salesforce.com/s/articleView?id=sfdo.pmm_configure_permission_sets.htm&release=264.0.0&type=5)** Assign permission sets to users based on their profiles. - **[A Note About Open Orgs](https://help.salesforce.com/s/articleView?id=sfdo.pmm_configure_permission_sets.htm&release=264.0.0&type=5)** If all users with a login to your Salesforce org can see all data in your org—that is, they can see all the records and fields—you have what's called an "open org." - **[Understand Access to Records](https://help.salesforce.com/s/articleView?id=sfdo.pmm_configure_permission_sets.htm&release=264.0.0&type=5)** Use sharing rules to expand access to additional groups of users. ## Program Management Module Permission Sets A user only needs one Program Management Module permission set; however, it can be combined with other product permission sets as needed. Users can have only one profile, but they can have multiple permission sets. You can assign permission sets to any user, regardless of their profile. PMM includes these permission sets:
Permission Set Access Assign To
PMM: Manage Read, Create, Edit, and Delete access on Programs, Program Engagements, Program Cohorts, Services, Service Deliveries, Service Participants, Service Schedules, and Service Sessions objects and fields.

People who set the direction of your programs and need to configure Programs, Services, Program Engagements, Program Cohorts, and Service Deliveries in your org. This includes Salesforce admins, program directors, and program managers.
PMM: Deliver

Read access on Programs, Program Cohorts, Services, and Service Schedules objects and fields. Read and Edit access on Service Sessions objects and fields. Create, Read, and Edit access on Program Engagements and Services Deliveries objects and fields.

Create, Read, and Edit access on Program Engagements, Services Deliveries, and Service Participants objects and fields.

 Font line staff, case managers, and service providers who deliver your programs and services. People with this permission can see but not modify Programs, Program Cohorts, and Services. They can create and modify Program Engagements and Service Deliveries to support their day-to-day work.
PMM: View Read access on Programs, Program Engagements, Program Cohorts, Services, Services Deliveries, Service Participants, Service Schedules, and Service Sessions objects and fields.

Executive staff, development directors, or others who need visibility into program performance and service delivery to clients, but don't actually provide these services. People with this permission can view but not modify PMM data.
![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-program_management_module-264-0-0-production-enus/443b48d5-82c1-45d8-a7f7-2c07521b8b28/images/icon_important.png) Important PMM permissions only apply to the custom objects in the PMM application. To address the object-level security for standard Salesforce objects such as Account, Contact, and Case, Admins must ensure that Read, Create, Edit, and Delete access is granted to the appropriate profiles. For more information, see [Control Who Sees What](https://help.salesforce.com/articleview?id=security_data_access.htm&type=5) in Salesforce Help. If you want to extend access to program management records beyond what is included in the permission sets, we recommend [adding sharing rules](https://help.salesforce.com/s/articleView?id=sfdo.pmm_create_shar_rules.htm&release=264.0.0&type=5 "Some organizations use a model where program managers share ownership of programs. Create sharing rules to let different program managers edit a client's program-related data."). ## Assign Permission Sets Assign permission sets to users based on their profiles. To assign permission sets: 1. Click ![Setup gear icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-program_management_module-264-0-0-production-enus/443b48d5-82c1-45d8-a7f7-2c07521b8b28/resources-product/images/setup.png), then click **Setup**. 2. From Setup, enter Permission Sets in the Quick Find box, then click **Permission Sets**. 3. Select the permission set that you want to assign to users. 4. Click **Manage Assignments**, then **Add Assignments**. 5. Select the checkboxes next to the appropriate users. 6. Click **Assign**. ## A Note About Open Orgs If all users with a login to your Salesforce org can see all data in your org—that is, they can see all the records and fields—you have what's called an "open org." PMM permission sets won’t limit user access in open orgs. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-program_management_module-264-0-0-production-enus/443b48d5-82c1-45d8-a7f7-2c07521b8b28/images/icon_note.png) Note Adding PMM to an existing NPSP open org results in open access for all users to all program management data. As an alternative, we recommend you use security and sharing settings to allow specific users to see records or fields based on criteria you specify. This more secure approach ensures client confidentiality, especially if you have general and fundraising staff using NPSP in your org. Assigning the Manage Programs permissions to your programs and management staff will keep your client data visibility restricted. ## Understand Access to Records Use sharing rules to expand access to additional groups of users. Each record owner can manually share individual records with other users by selecting the Share button on the record. However, it’s often more efficient for an admin to share records with defined groups of users. What does this mean for NPSP and PMM? - Additional permissions can be granted by assigning permission sets to users. - Access to records a user doesn’t own is first assigned by org-wide defaults. In PMM, these are public read/write. This means that all users who have access to the objects can view records for those objects, but only the record owners can edit them. Although these are the default settings, you may not want all users in your org to be able to see or edit records. Take some time to think about your sharing model and decide if you want to make it more restrictive.