You are here:
Membership Processing Best Practices
Processing membership when many members are added in a single transaction can result in significant lockout times. Limiting the number of users per transaction can speed up processing time. Follow these best practices to minimize the impact of processing times on members.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
- Plan Ahead of the Go Live Date
- A few things to keep in mind when planning to add or remove members to a site or portal:
- The number of members that are added or removed affects the processing time. The more
members that are processed, the more time it takes to complete the process. When processing
over a million users, the processing time can take hours.
Note Governor limits ensure that only 10 million users are processed at a time. Attempting to process more than 10 million at a time results in an error. - When processing members, the site or portal is locked and admins can’t make more changes to it. New Experience Cloud site members aren’t able to access the site until processing is complete, but existing members still have access. Plan for a maintenance window and communicate as necessary with your members.
- To get an approximate estimate of the processing time, test the deployment in a sandbox environment with a similar setup before deploying in production.
- Schedule membership updates for a time when traffic in the site is known to be low.
- The number of members that are added or removed affects the processing time. The more
members that are processed, the more time it takes to complete the process. When processing
over a million users, the processing time can take hours.
- Organize Members into Smaller Groups
- Organizing members into smaller groups cuts down on processing time. The following
strategies can help reduce the number of members being processed at a time:
- Membership processing adds both active and inactive members of a profile or permission set to the portal or site. Remove inactive members from profiles and permission sets if you don’t need to track them.
- Go live with high-priority members first. Then add the rest of the group in order of priority.
- Add profiles and permission sets in small batches. For example, if you’re adding 10 million members, put them into buckets of 1 million per profile or permission set.
- Removing profiles or permission sets from the portal or site takes longer than adding them. Make sure that those profiles or permission sets are required before you add them so you don’t have to remove them later.
- Other Considerations
- When processing members:
- Don’t add and remove profiles or permission sets at the same time.
- Don’t add or remove users from profiles or permission sets while membership is processing.
- Don’t allow user self-registration while membership is processing.
Did this article solve your issue?
Let us know so we can improve!
