In evaluating the scenario presented where multiple external sources and objects are being integrated into CRM Analytics, we need to consider the total number of enabled objects across all connections. Here's a breakdown:
10 objects from an external database
12 objects each from three external Salesforce environments, totaling 36 objects
15 objects each from two external Salesforce environments, totaling 30 objects
25 objects already enabled from the local Salesforce connector
This brings us to a total of 101 objects enabled, which may exceed typical limits on the number of objects that can be enabled in a CRM Analytics environment, depending on the specific Salesforce licensing and platform limits.

In CRM Analytics, you can control the visibility of dashboards and other assets using the asset visibility feature. This allows the consultant to restrict access to specific assets (like dashboards) for certain groups of users, such as sales reps, without needing to duplicate datasets or move dashboards to another app. This is the most efficient way to manage access for dashboards in progress while allowing only sales managers to view the in-progress dashboards.

When a record exceeds 400 sharing descriptors, it can cause performance issues or sharing rule complications in CRM Analytics. In such cases, the recommended solution is to use security predicates, which allow fine-tuned control over which data is visible to users based on their sharing rules and permissions. Security predicates reduce the number of sharing descriptors by enforcing security at the dataset level rather than relying solely on record-sharing mechanisms.
Increasing the sharing descriptor limit is not an available option, and Salesforce Support does not typically increase this limit, making the use of security predicates the best approach.