Two Community licenses that allow records to be shared with a criteria-based sharing rule are Partner Community and Customer Community Plus. These license types allow users to access custom objects and a subset of standard CRM objects, such as accounts, contacts, cases, and dashboards. These license types also support advanced sharing features, such as role hierarchy, sharing rules, manual sharing, and Apex sharing.

UMS can accomplish three goals with Experience Cloud moderation functionality:

Track Flagging and moderation activity within the Experience site. Moderation functionality allows UMS to view reports and dashboards that show the flagging and moderation activity on its site, such as the number of flagged items, the number of moderated items, and the flagging reasons.

Allow members to flag posts comments files, and messages that are inappropriate or spam. Moderation functionality allows UMS to enable members to flag content that violates the site's guidelines or policies. Members can choose a flagging reason from a predefined list or enter their own reason.

Designer specific users as moderators so that they can closely monitor the size. Moderation functionality allows UMS to assign specific users as moderators who have permission to manage content on its site. Moderators can review flagged items, delete or edit inappropriate content, ban or warn abusive users, or escalate issues to administrators.

Two Salesforce recommendations for setting up partner roles in large orgs are B and C. Partner roles are roles that are assigned to partner users who access your Experience Cloud site through a partner account. A partner account is an account that has the Is Partner checkbox enabled. To set up partner roles, you should create them in a separate branch in your Role Hierarchy, which allows you to isolate partner data from internal data and control partner visibility and access. You should also grant partner users access to the partner account using a Sharing Rule, which allows you to share records owned by internal users with partner users based on criteria that you define.

To implement SAML 550 for the Experience Cloud site, the UC administrator should use the site login URL as an endpoint where SAML assertion is made. SAML 550 is a protocol that allows users to authenticate with a third-party identity provider and access Salesforce resources without entering their Salesforce credentials. The site login URL is the URL that users use to access the Experience Cloud site. By using the site login URL as an endpoint, the UC administrator can configure SAML settings to redirect users to the identity provider for authentication and then back to the Experience Cloud site.

To make a Knowledge article visible to both authenticated customers and unauthenticated guest users on the public knowledge base, you need to select the Visible to Public Knowledge Base checkbox when creating the article. This will allow you to share the article with public users on your site. You can also select other visibility options, such as Visible to Customer or Visible to Partner, if you want to share the article with other channels.