Explanation
Box 1: Upload the theme elements as new web resources.
Each type of icon is stored as a web resource. Create a web resource first and then set the icons to use them.
Alternatively, you can add the icon by creating a new web resource when you define the table properties.
Box 2: Replace an existing UI item's hexadecimal number.
Copy and alter the existing theme
The easiest and quickest way to create a new theme is to clone and alter an existing theme. Then save, preview, and publish it.
* Sign in to Power Apps, select Settings icon (upper right), and then select Advanced settings.
* Select Customizations, and then select Themes.
* Under All themes, select the theme you want to clone, such as the CRM Default Theme. Select Clone on the command bar.
* Replace an existing UI item's hexadecimal number, such as the Title Text Color, with the hexadecimal value that represents the color you want.
For example, the CRM Default Theme was cloned and changed using mostly varying shades of green color.
The following screenshots show the new colors for navigation and highlighting. A custom logo was also added that will appear in the upper left corner of an app.


Reference:
https://docs.microsoft.com/en-us/power-apps/maker/model-driven-apps/create-themes-organization-branding

Explanation
Power BI uses Azure Active Directory (AAD) to authenticate users who sign in to the Power BI service, and in turn, uses the Power BI login credentials whenever a user attempts to access resources that require authentication. Users sign in to the Power BI service using the email address used to establish their Power BI account; Power BI uses that login email as the effective username, which is passed to resources whenever a user attempts to connect to data. The effective username is then mapped to a User Principal Name (UPN) and resolved to the associated Windows domain account, against which authentication is applied.
Reference: https://docs.microsoft.com/en-us/power-bi/enterprise/service-admin-power-bi-security

Explanation
Box 1: Assign records to a service account and add the team member doing the verification by using an access team.
When to use access teams
* The teams are dynamically formed and dissolved. This typically happens if the clear criteria for defining the teams, such as established territory, product, or volume aren't provided.
* The team members require different access rights on the records. You can share a record with several access teams, each team providing different access rights on the record. For example, one team is granted the Read access right on the account and another team, the Read, Write and Share access rights on the same account.
* A unique set of users requires access to a single record without having an ownership of the record.
Box 2: Assign records to the QV team when the service request is completed.
Issues: More employees than are required can access individual client information and continue to have access after a service request is completed.
Management has decided to create a new qualification verification (QV) role to help ensure that clients get the most accurate results. This role examines completed work to ensure that nothing is missed.
* When users go on vacation, all their outstanding Service Request records are assigned to a substitute employee. The substitute employees are unable to see all the qualifications related to their service requests.
Reference:
https://docs.microsoft.com/en-us/power-apps/developer/data-platform/use-access-teams-owner-teams-collaborate

Explanation
Step 1 (B): Here's how we embed PowerApps into a Power BI report:
* Download and login to the Power BI desktop application
* Click on (...) and select "Import from the marketplace."
Step 2: Open Power BI desktop and use "Get data" to connect with the Common Data Service data source.
Step 3: Publish the report to Power BI service.
Reference:
https://purple.telstra.com/blog/powerbi-integration-with-powerapps