Explanation
Text Description automatically generated

Box 1: N:1
You add a lookup column with a many-to-one relationship.
Box 2: N:N
Box 3: N:1
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/data-platform-entity-lookup

Explanation
https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/webpage-access-control

Explanation
A: Deleting by table allows you to select specific tables in the Dataverse database for which you want to delete the auditing data. This can be done by going to the Power Apps portal, navigating to the Data tab, and selecting the table for which you want to delete the auditing data. You can then select the specific auditing data you want to delete and click the "Delete" button. This is useful if you want to only delete auditing data for specific tables and not for the entire database. Reference:
https://docs.microsoft.com/en-us/power-platform/admin/data/data-management-auditing#delete-audit-logs
C: Deleting between two specified dates allows you to select a range of dates within which the auditing data will be deleted. This can be done by going to the Power Apps portal, navigating to the Data tab, and selecting the "Audit" option. From there, you can select the "Delete" button, and select the "Between two dates" option.
Then you can specify the start and end date for which you want to delete the auditing data. This is useful if you want to delete auditing data for a specific time period and not for the entire database. Reference:
https://docs.microsoft.com/en-us/power-platform/admin/data/data-management-auditing#delete-audit-logs
E: Deleting older than a specified date allows you to select a specific date, and any data older than that date will be deleted. This can be done by going to the Power Apps portal, navigating to the Data tab, and selecting the "Audit" option. From there, you can select the "Delete" button, and select the "Older than a specified date" option. Then you can specify the date for which you want to delete the auditing data. This is useful if you want to delete auditing data that is older than a certain date and not for the entire database. Reference:
https://docs.microsoft.com/en-us/power-platform/admin/data/data-management-auditing#delete-audit-logs It's always good to have a backup of Data before deletion and also check the retention period of the data you want to delete.

Explanation

Reference:
https://docs.microsoft.com/en-us/power-virtual-agents/advanced-hand-off

Explanation
Box 1: Move the manager and reports to a separate business unit.
Keep the Manager hierarchy, and put the reports to the appropriate business unit.
Note: Two security models can be used for hierarchies, the Manager hierarchy and the Position hierarchy.
With the Manager hierarchy, a manager must be within the same business unit as the report, or in the parent business unit of the report's business unit, to have access to the report's data. The Position hierarchy allows data access across business units. If you are a financial organization, you may prefer the Manager hierarchy model, to prevent managers' accessing data outside of their business units. However, if you are a part of a customer service organization and want the managers to access service cases handled in different business units, the Position hierarchy may work better for you.
Box 2: Add the CEO to the representative user record as a manager.
Set up Manager and Position hierarchies
The Manager hierarchy is easily created by using the manager relationship on the system user record. You use the Manager (ParentsystemuserID) lookup field to specify the manager of the user.
Note: Depth is used to limit how many levels deep a manager has Read-only access to the data of their reports.
For example, if the depth is set to 2, the CEO can see the data of the VP of Sales, VP of Service and Sales and Service Managers. However, the CEO doesn't see the Sales data or the Support data.

Box 3: Add users to field security
Power Platform's field-level security lets you set which fields users can see or edit.
Reference: https://docs.microsoft.com/en-us/power-platform/admin/hierarchy-security
https://docs.microsoft.com/en-us/power-platform/admin/field-level-security