1. While browsing the app, open the dashboard in view mode.The dashboard inspector is not available while running the app, editing the dashboard, or previewing an embedded dashboard outside of Analytics.
2. To open the dashboard inspector, click and thenDashboard Inspector.
3. To review the dashboard-level performance, open the Performance tab in the dashboard inspector.
4. Click Run Performance Check. The Performance Factors section shows all factors by which the dashboard is evaluated. Note If your dashboard contains multiple pages, the dashboardinspector shows results for the current page being viewed.
5. If a warning icon () appears next to a factor, expand the factor to learn how to fix the issue to improve the dashboard’s performance.Ignore the factors with a green checkmark () because these issues don’t apply to the dashboard.
6. To analyze the performance of all steps in the dashboard, click the Steps tab.The table lists all steps that ran when the dashboard loaded. If the dashboard containsmultiple pages, the table lists the steps that ran for the current page. Each time youswitch pages, newly run steps are added to the table, and previously run steps, whichare no longer used, are listed as unused. The table shows the following metrics for each step. MetricDescription# RunsNumber of times the step ran. Steps may run multiple times because of faceting or bindings. This number includes step runs that execute the query or use cached results.First (MS)Number of milliseconds to run the step for the first time. The first run typically, but not always, executes the query.Avg (MS)Average number of milliseconds to run the query. Only step runs that execute the query are included in this calculation.
7. Select a step in the table to view additional details about the query and the last run.For more information about step performance, see Optimize a Step.

---

1. From the Account Team related list on an account, click to either add a team member or a default account team. If you don’t see the Account Teams related list, ask your admin to add it to your page layout.
2. Fill in the information, including the user or default team. High-volume portal users can’t be added to teams.Note The access level can’t be less restrictive than your org’s default account access level. The options available to you vary depending on your org’s sharing model and whether you’re using Salesforce Classic or Lightning Experience. Regardless of sharing access, account team members must also have the Read permission on accounts to view accounts that list them as members.
3. Save the information.

---

1. Navigate to the Status tab in Personalization Builder.
2. Click .
3. Click Notification Settings.
4. Enter at least one email address.
5. Select the number of hours to delay the error notification.
6. Enter the Collect Tracking Codes to monitor.
7. Click Save.

---

1. Note To use automatic topic assignments, you must first enable CommunityWorkspaces in Community Settings.Open Community Management.
2. Access Automatic Topic Assignment by clicking Content Targeting | Topics | Automatic Topic Assignment.
3. Enable Automatic Topic Assignment.
4. Select a data category group and a data category.
5. Add the topics that you want to assign to the articles under that data category.
6. Select the option to add the topics to existing articles in the data category. The topics are then assigned to all articles in all data categories under the data category group. If you don’t select this option, the topics are added only to new articles added to the data category, and the existing articles remain unchanged.
7. Click Save.

---

1. Select a record type or business process and click Edit next to the picklist field to change its values.
2. Add or remove values as needed. Users can choose from these values when creating or editing records.
3. Optionally, choose a default picklist value. Some picklists require a default value. The default value in a dependent field is ignored.
4. Click Save.

---

1. From Setup, enter Permission Sets in the Quick Find box, then select Permission Sets, then click New.
2. Create a permission set that includes the appropriate permissions.
3. From Setup, enter Users in the Quick Find box, then select Users.
4. Find the user you want to be a community moderator and add the permission set to their Permission Set Assignments related list.

---

1. On the login page, click the forgot password link.
2. Enter your username and click Continue. An email containing instructions to reset your password is sent to the address specified in your Salesforce personal settings.
3. Within 24 hours, click the link provided in the email, answer your security question, and click Continue. (The link in the email can be used only once, and expires after 24 hours.)
4. When prompted, enter a new password.

---

Supported Editions - both Salesforce Classic and Lightning Experience, All Editions

1. Determine themember’s workspace permissions level. Determine if the member is an Admin, Contributor, or a Limited Member?

---

1. From Setup, enter Apex Classes in the Quick Find box, then selectApex Classes.
2. Edit the generated Apex SAML JIT handler to map fields between SAML and Salesforce. In addition, you can modify the generated code to support the following:Custom fieldsFuzzy profile matchingFuzzy role matchingContact lookup by emailAccount lookup by account numberStandard user provisioning into a communityStandard user login into a communityDefault profile ID usage for portal Just-in-Time provisioningDefault portal role usage for portal Just-in-Time provisioningUsername generation for portal Just-in-Time provisioningFor example, to support custom fields in the generated handler code, find the“Handle custom fields here” comment in the generated code. After that code comment,insert your custom field code. For more information and examples, see the SamlJitHandler Interface documentation.
3. Custom fields
4. Fuzzy profile matching
5. Fuzzy role matching
6. Contact lookup by email
7. Account lookup by account number
8. Standard user provisioning into a community
9. Standard user login into a community
10. Default profile ID usage for portal Just-in-Time provisioning
11. Default portal role usage for portal Just-in-Time provisioning
12. Username generation for portal Just-in-Time provisioning

---

1. Non-scope by user
2. Scope by user

---