AWS partner-central medium security documentation change
Summary
Updated permission set documentation with corrected capitalization, clarified terminology, and added details about named credentials setup
Security assessment
Added reference to named credentials setup which relates to authentication security. Emphasized recommendation to set sync log records as private due to containing sensitive opportunity information. These changes demonstrate security-conscious documentation improvements.
Diff
diff --git a/partner-central/latest/crm/crm-connector-pemissions-sets.md b/partner-central/latest/crm/crm-connector-pemissions-sets.md index 02077867e..c85f4e788 100644 --- a//partner-central/latest/crm/crm-connector-pemissions-sets.md +++ b//partner-central/latest/crm/crm-connector-pemissions-sets.md @@ -5 +5 @@ -Business administrator (APN business administrator)Integration user (APN integration user)Business user (APN business user)System permissions to view reportsActivate flow user +Business administrator (APN Business Administrator)Integration User (APN Integration User)Business user (APN Business User)Granting permissions to view reportsActivating flow users @@ -7 +7 @@ Business administrator (APN business administrator)Integration user (APN integra -# Permissions sets +# AWS Partner Network permission sets @@ -9 +9 @@ Business administrator (APN business administrator)Integration user (APN integra -Three primary AWS Partner personas are supported in the AWS Partner Customer Relationship Management (CRM) connector application. These can be implemented by the AWS Partner by giving the designated Salesforce user the corresponding permission set from the app. +The CRM connector supports the following primary AWS Partner Network personas: @@ -13 +13 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * Business administrator (APN business administrator) + * Business administrator (APN Business Administrator) @@ -15 +15 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * Integration user (APN integration user) + * Integration User (APN Integration User) @@ -17 +17 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * Business user (APN business user) + * Business user (APN Business User) @@ -19 +19 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * System permissions to view reports + * Granting permissions to view reports @@ -21 +21 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * Activate flow user + * Activating flow users @@ -26 +26 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel -## Business administrator (APN business administrator) +## Business administrator (APN Business Administrator) @@ -28 +28 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * Should be given to a system admin or a business admin to configure the setup/mapping of records. + * Assign to a system admin or a business admin to configure the setup and mapping of records. @@ -30 +30 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * Gives full access to the Salesforce AWS Partner Network (APN) CRM administration app. + * Gives full access to the Salesforce AWS Partner Network CRM administration app. @@ -36 +36 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * Doesn’t allow the user to schedule the integration, only to set up configurations. + * Doesn’t allow the user to schedule an integration, only to set up configurations. @@ -38 +38 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * Doesn’t give core Salesforce setup access. + * Doesn’t provide core Salesforce setup access. @@ -40 +40 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * There are some settings in Salesforce that require additional access, specifically named credentials and custom settings that the AWS Partner must provide to their user. But if this permission set is paired with a Salesforce system admin profile, all of the necessary permissions to configure the application should function. + * Some settings in Salesforce require additional access. Specifically, named credentials and custom settings that the AWS Partner must provide to their user. However, partners can pair this permission set with a Salesforce system admin profile and enable all of the necessary permissions to configure the application. For more information about named credentials, refer to [Set up named credentials](./set-up-api-credentials.html) @@ -45 +45 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel -## Integration user (APN integration user) +## Integration User (APN Integration User) @@ -47 +47 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * Should be assigned to a designated system user that’s responsible for processing the integration. + * Assign to a system user responsible for processing the integration. @@ -49 +49 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * To schedule the integration, a Salesforce system admin should log in as this user and invoke the system integration schedule. + * To schedule an integration, a Salesforce system admin signs in as this user and invokes the system integration schedule. @@ -51 +51 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * Allows for full access to configure the mappings, as well as invoke setting up the schedule. + * Allows admins to configure the mappings and invoke integration schedules. @@ -53 +53 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * The integration may break if this permission isn’t set on the user responsible for running the integration. + * The integration may break if this permission isn’t set for the user who runs the integration. @@ -55 +55 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * In addition to this permission set, the user designated to process the integration should be given field level access to all mapped fields. If this isn’t done, the mappings will fail to sync as assigned. + * In addition to this permission set, the user designated to process the integration should have field level access to all mapped fields. If not, the mappings fail to sync as assigned. @@ -62 +62 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel -## Business user (APN business user) +## Business user (APN Business User) @@ -64 +64 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * Can be assigned to business users who might want to see the sync log details related to their opportunities. This allows for end user troubleshooting if data is not syncing correctly. + * Assign to business users who might want to see the sync log details related to their opportunities. This allows for end-user troubleshooting if data is not syncing correctly. @@ -68 +68 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * We recommend that sync log records are set to private, since they contain sensitive opportunity information. + * We recommend setting sync log records to private, since they contain sensitive opportunity information. @@ -70 +70 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel - * If a private model is configured, APN business users can access only the records if the partner Salesforce administrator configures record sharing with users. + * If you configure a private model, APN business users can access only the records if the partner Salesforce administrator configures record sharing with users. @@ -75 +75 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel -## System permissions to view reports +## Granting permissions to view reports @@ -77 +77 @@ Three primary AWS Partner personas are supported in the AWS Partner Customer Rel -To allow a user to view reports on the **Home** tab of the AWS Partner CRM connector, an administrator must grant them the following permissions: +To allow a user to view reports on the **Home** tab of the AWS Partner CRM connector, an administrator must grant the following permissions: @@ -92 +92 @@ To allow a user to view reports on the **Home** tab of the AWS Partner CRM conne -For more information, refer to [Grant Users Access to Reports and Dashboards](https://help.salesforce.com/s/articleView?id=sfdo.PMM_Folder_Sharing_Reports_Dash.htm). +For more information, refer to [Grant Users Access to Reports and Dashboards](https://help.salesforce.com/s/articleView?id=sfdo.PMM_Folder_Sharing_Reports_Dash.htm) in the Salesforce help. @@ -94 +94 @@ For more information, refer to [Grant Users Access to Reports and Dashboards](ht -## Activate flow user +## Activating flow users @@ -96 +96 @@ For more information, refer to [Grant Users Access to Reports and Dashboards](ht -To allow a user to run flows and the **Link private offer** button on an ACE opportunity, the system administrator must configure the user as a flow user. +Activating users as flow users enables them to run flows and use the **Link private offer** button on an ACE opportunity. @@ -98 +98 @@ To allow a user to run flows and the **Link private offer** button on an ACE opp - 1. Ensure that the system administrator the correct permissions to assign a flow user. For more information, refer to [Add Run Flows Permissions](https://help.salesforce.com/s/articleView?id=sf.wcc_setup_add_run_flows_perms.htm). + 1. Ensure that the system administrator has permission to assign a flow user. For more information, refer to [Add Run Flows Permissions](https://help.salesforce.com/s/articleView?id=sf.wcc_setup_add_run_flows_perms.htm) in the Salesforce help. @@ -115 +115 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Prerequisites +Personas for CRM connector permission sets @@ -117 +117 @@ Prerequisites -Guided setup +AWS Marketplace permission sets