Scenario: When identifying versions of the app solution, all dependencies, entities, and user interfaces components must be identified to avoid any unintentional issues caused by reverting individual components to a previous version.

Power Apps has added components to the rule set that encourages best practices in the Power Apps Checker. You can check your canvas apps and flows that are included in solutions and then review all issues in a single, consolidated report.

Graphical user interface, text, application, email Description automatically generated

Box 1: Security role

Scenario: Employees must only be able to access their own time tracking records from the app.

Testers report that they can see time entries in the Time Tracker app, not just their own.

Box 2: Field-level security

Scenario: Employees must only be able to modify time records for the current and previous day.

Testers report that they can edit any existing time entries.

Box 3: Hierarchical security

You use field security tables to apply field-level security, which restricts field access to specified users and teams.

Graphical user interface, text, application Description automatically generated

Box 1: Model-driven app in Microsoft Teams

A user's ability to see and use apps is controlled by sharing the application with the user. Sharing of canvas apps is done directly with a user or Azure AD group but is still subject to Dataverse security roles. Sharing of model-driven apps is done via Dataverse security roles.

Box 2: Sharepoint Calendar