Graphical user interface, text, application, email
Description automatically generated
References:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/field-security-entities

Graphical user interface, text, application, email
Description automatically generated
Box 1: Field security profile
Record-level permissions are granted at the entity level, but you may have certain fields
associated with an entity that contain data that is more sensitive than the other fields. For
these situations, you use field-level security to control access to specific fields.
Field-level security is available for the default fields on most out-of-box entities, custom
fields, and custom fields on custom entities. Field-level security is managed by the security
profiles.
Box 2: Compliancy policy
Compliance policy settings – Tenant-wide settings that are like a built-in compliance policy
that every device receives. Compliance policy settings set a baseline for how compliance
policy works in your Intune environment, including whether devices that haven’t received any device compliance policies are compliant or noncompliant.
Note: Mobile device management (MDM) solutions like Intune can help protect
organizational data by requiring users and devices to meet some requirements. In Intune,
this feature is called compliance policies.
Compliance policies in Intune:
Define the rules and settings that users and devices must meet to be compliant.
Include actions that apply to devices that are noncompliant. Actions for noncompliance can
alert users to the conditions of noncompliance and safeguard data on noncompliant
devices.
Can be combined with Conditional Access, which can then block users and devices that
don't meet the rules.

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

Box 1: Contact
With Contact scope, a signed-in user in the role for which the permission record is defined
will have the rights granted by that permission only for records that are related to that
user's contact record via a defined relationship.
Box 2: Account
With Account Scope, a signed-in user in the role for which the permission record is defined
will have the rights granted by that permission only for records that are related to that
user's parent account record via a defined relationship.
This scope means that the entity list will only show the records of the selected entity that
are associated to the user's parent account. For example, if an entity permission allows
Read access to Lead entity with the Account scope, the user having this permission can
view all the leads of only the parent account of the user.

Graphical user interface, application, table
Description automatically generated
Box 1: Power Platform Local Business Owner Team
Owner team: An owner team owns records and has security roles assigned to the team. A
user's privileges can come from their individual security roles, those of the teams that
they're part of or the ones they inherit. A team has full access rights on the records that the
team owns. Team members are added manually to the owner team.
Scenario: Employee authentication with the existing system is provided by an on-premises
Active Directory instance that is linked to Azure Active Directory.
Box 2: Azure Active Directory Security Group Team

An Azure Active Directory (Azure AD) group team. Similar to owner team, an Azure AD
group team can own records and can have security roles assigned to the team.
Note: The administration of app and data access for Microsoft Dataverse has been
extended to allow administrators to use their organization's Azure Active Directory (Azure
AD) groups to manage access rights for licensed Dataverse users.
Box 3: Azure Active Directory B2B Guest Access
An Azure AD B2B collaboration user is an external user, typically from a partner
organization, that you invite to sign into your Azure AD organization using their own
credentials. This B2B collaboration user (also generally referred to as a guest user) can
then access the apps and resources you want to share with them. A user object is created
for the B2B collaboration user in the same directory as your employees. B2B collaboration
user objects have limited privileges in your directory by default, and they can be managed
like employees, added to groups, and so on.
Scenario: Before First Up signs a contract to place workers at a client company, a member
of the audit team visits the company and interviews company management. Audit members
use different types of devices including Android and iOS devices. First Up has no plans to
require the use of a single type of device.

B.

customer maintenance procedures

D.

solution regulatory compliance

E.

time-to-load forms

Non-functional requirements capture the elements that users might not directly care about
but are important to support the proposed architecture and operational viability of the
solution. Non-functional requirements often influence user adoption and perceived
satisfaction with the solution.
Examples of common non-functional requirement types include:
Availability
Compliance/regulatory
Data retention/residency
Performance (response time, and so on)
Privacy
Recovery time
Security
Scalability
Reference:
https://docs.microsoft.com/en-us/learn/modules/work-with-requirements/4-non-functionalrequirements

A.

Canvas app within Power Apps Player

B.

Canvas app within a browser

Audit teams must have the ability to view worker information on their mobile devices.
Audit teams must be able to record data during visits to locations where workers are
placed.
When you create an app, or someone shares an app with you, you can run that app on the
Power Apps mobile app or in a web browser.
Reference:
https://docs.microsoft.com/en-us/powerapps/user/run-app-browser