Reference:
https://docs.microsoft.com/en-us/power-bi/collaborate-share/service-share-dashboards

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
A solution publisher includes a prefix. The publisher prefix is a mechanism to help avoid naming collisions.
This allows for solutions from different publishers to be installed in an environment with few conflicts. For example, the Contoso solution displayed here includes a solution publisher prefix of contoso.
e: https://docs.microsoft.com/en-us/power-platform/alm/solution-concepts-alm

Explanation
Instead, create a custom Age group entity and synonyms for each individual age in the corresponding item.
Use Age group for Identify in the question.
The prebuilt entities cover commonly used information types, but on some occasions, such as when building a bot that serves a specific purpose, you'll need to teach the bot's language understanding model some domain-specific knowledge.
To do this, you need to create a custom entity.
Reference:
https://docs.microsoft.com/en-us/power-virtual-agents/advanced-entities-slot-filling

Explanation
Graphical user interface, application Description automatically generated

Box 1: Use the demo website
When publishing the bot to the web, you can publish to a prebuilt demo website (which you can use to share the bot with your teammates and stakeholders) and to your own live website.
Box 2: Share the chatbot to a security group containing all users.
A license for each user, also known as a "per user license" (or "Power Virtual Agent User License" as referred to on the Microsoft 365 admin center), should be assigned to individual users who need access to create and manage chatbots.
To simplify user license management, you can assign licenses to an Azure Active Directory (Azure AD) security group.
Box 3: Embed the chatbot code in an IFRame on your copany's public website You can add your bot to a live website as an IFrame. Your live website can be a customer-facing external website or an internal site, like a SharePoint or Yammer site.
Reference:
https://docs.microsoft.com/en-us/power-virtual-agents/publication-connect-bot-to-web-channels
https://docs.microsoft.com/en-us/power-virtual-agents/requirements-licensing