Before beginning work on these sites, the consultant should notify the stakeholders that the number of both moderation and rate rules exceeds the org limit. Moderation rules are rules that flag or block content based on keywords, phrases, or patterns. Rate rules are rules that limit the number of posts or comments a user can make in a given time period. The org limit for moderation rules is 10 and the org limit for rate rules is 5. Since each site needs 3 moderation rules and 4 rate rules, the total number of rules for 5 sites is 15 moderation rules and 20 rate rules, which exceed the org limit.

To meet the requirement of distributing leads to partners, UMS needs to take at least three steps:
Create a Lead Process for Lead Distribution. A lead process is a set of stages that a lead goes through from creation to conversion. UMS can create a lead process that defines how leads are distributed to partners based on criteria such as region, industry, or product.
Create a Lead Queue for Lead Distribution. A lead queue is a list of leads that are assigned to a group of users who share the workload. UMS can create a lead queue for its partners and assign leads to the queue based on the lead process.
Configure Lead creation Leadon low Distribution inside PRM Workspace. PRM Workspace is a feature that allows UMS to manage its partner relationships, such as recruiting, onboarding, training, and co-selling. UMS can configure lead creation and distribution settings inside PRM Workspace, such as enabling partners to create their own leads, setting up lead assignment rules, and defining lead notification preferences.

These two options allow the article to be visible to internal Salesforce users, unauthenticated visitors to the site, and third-party authenticated users. Visible in Public Knowledge Base enables the article to be accessed by guest users without logging in, while Visible to Employee enables the article to be accessed by internal users with the appropriate permissions4

To meet the requirements for both personas, GCC should create a portal for external researchers and give internal staff access to the main org. This will allow GCC to provide different features and permissions for each persona, as well as enable collaboration between them in a private Chatter group. For example, GCC can create a portal for external researchers using the Partner Central template, where they can view and update financial data, access reports and dashboards, and join Chatter groups. GCC can also give internal staff access to the main org using standard user licenses, where they can manage portfolio data, create workflows and processes, and join Chatter groups.