You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: powerapps-docs/sample-apps/regional-emergency-response/configure.md
+40-5Lines changed: 40 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ manager: annbe
6
6
ms.service: powerapps
7
7
ms.topic: conceptual
8
8
ms.custom:
9
-
ms.date: 04/22/2020
9
+
ms.date: 05/06/2020
10
10
ms.author: kvivek
11
11
ms.reviewer: kvivek
12
12
searchScope:
@@ -37,12 +37,11 @@ When you sign into the admin (model-driven) app, you will see the entities in th
37
37
38
38
-**Hierarchy area**: Data for entities in this area can be added either by importing data from the sample data files or manually. The entities under the **Hierarchy** area are listed in the order you should populate data. Also, parent org admins (hospital admins) can view and manage data under the following entities for their hospital from the portal: **Systems**, **Regions**, and **Facilities**.
39
39
40
-
> [!NOTE]
41
-
> We provide name and FIPS code for all the counties in the Washington state as sample data that you can import. To obtain data counties in other states, visit <https://www.census.gov/geographies/reference-files/2018/demo/popest/2018-fips.html>
42
-
43
40
-**Admin Entities area**: Data in the **Supplies** entity is added by importing data from the sample data file. You can manually add and manage supplies data later.
44
41
45
-
-**Customers area**: You use the **Portal Users** entity to add and manage portal users. More information: [Manage portal users](#manage-portal-users)
42
+
-**Customers area**: You use **Portal Users** to [manage portal users](#manage-portal-users) and **User Requests** to [manage portal user requests](#manage-portal-user-requests).
43
+
44
+
-**Resources area**: Select **Documentation** to view this document.
46
45
47
46
There are two ways in which you can add master data to entities in the app:
48
47
@@ -295,6 +294,42 @@ Depending on the roles(s) you granted to the user, she/he will view respective a
295
294
296
295
An email will be sent automatically to the newly created user with an invitation code to join portals. The portal user can redeem the invitation to sign in and start using the portal. More information: [Get started with the portal](/powerapps/sample-apps/regional-emergency-response/portals-admin-reporting#getting-started-with-the-portal)
297
296
297
+
## Manage portal user requests
298
+
299
+
You can view, approve, and decline portal user requests using the **User Requests** option.
300
+
301
+
Use the appropriate view to view a list of approved, declined, inactive, and pending user requests.
302
+
303
+
> [!div class="mx-imgBorder"]
304
+
> 
305
+
306
+
### Approve or decline user request
307
+
308
+
To approve or decline user requests:
309
+
310
+
1. Sign into the admin app using the URL provided by your IT admin.
311
+
312
+
2. In the left pane, select **User Requests**, and then select **Pending Portal User Requests** view. You see a list of portal user requests pending for approval.
313
+
314
+
3. Double-click a user request to open it.
315
+
316
+
4. On the user request form:
317
+
318
+
1. Select the appropriate roles for the user in the **Choose roles for the user** area. To grant or deny a role, select **Yes** or **No** respectively for each role.
319
+
320
+
1. From the **Request State** list, select **Approve** or **Decline**.
321
+
322
+
1. Select the save icon in the lower-right corner.
323
+
324
+
> [!div class="mx-imgBorder"]
325
+
> 
326
+
327
+
Based on the approval or decline, the following happens:
328
+
329
+
- If you *approve* the access request, the user record is created with selected roles and the user receives an email with invitation code. The user can redeem the invitation code to sign in to the portal. More information: [Redeem invitation](portals-admin-reporting.md#redeem-invitation)
330
+
331
+
- If you *decline* the access request, the user record isn't created, and the user receives an email stating that the request is declined.
332
+
298
333
## View the Power BI dashboard
299
334
300
335
Business admins in the regional organization can view the Power BI dashboard in their Power BI tenant if the regional IT admin published the report as an app and granted access to business admins. More information: [Step 5: Configure and publish Power BI dashboard](deploy.md#step-5-configure-and-publish-power-bi-dashboard)
> 
650
649
651
650
## Step 12: Verify Assign Web Roles to New Users process is enabled
652
651
@@ -666,7 +665,7 @@ In this step, we will fix the **Send Password Reset To Contact** process to spec
666
665
667
666
5. If it’s not enabled, select the process name to open the record, and then select **Activate**. Confirm to activate the process.
668
667
669
-
## Step 13: Verify the Flow supply tracking flow is enabled
668
+
## Step 13: Enable the Flow supply tracking flow
670
669
671
670
1. Sign into [Power Automate](https://flow.microsoft.com/).
672
671
@@ -675,16 +674,72 @@ In this step, we will fix the **Send Password Reset To Contact** process to spec
675
674
> [!div class="mx-imgBorder"]
676
675
> 
677
676
678
-
3. In the solution, filter on **Flow** to find the **Flow supply tracking** record. Ensure that the status is set to **On**.
677
+
3. In the solution, filter on **Flow** to find the **Flow supply tracking** record.
679
678
680
679
> [!div class="mx-imgBorder"]
681
680
> 
682
681
683
-
4.If it is not set to **On**, select the flow name to open the flow definition.
682
+
4.Select the flow name to open the flow definition. In the flow definition, select **Edit** on the toolbar.
684
683
685
-
5.In the flow definition, select **Turn On** in the toolbar.
684
+
5.Fix the connection to connect to Common Data Service, and save the connection information.
686
685
687
-
## Step 14: Share admin app with other admin users
686
+
6. In the flow definition, select **Turn On**.
687
+
688
+
## Step 14: Update the details of flows for sending emails
689
+
690
+
In this step, we are going to do the following:
691
+
692
+
|Flow name|Changes|
693
+
|--|--|
694
+
|**Portal User Request: Send Email on Decline Request**|Update the connection to connect to Common Data Service and then specify a user account to send emails.|
695
+
|**Portal User Request: Send Email to Admins on Request Creation**|Update the connection to connect to Common Data Service and then specify a user account to send emails. Additionally, update the portal URL in the email body as per your Portal URL.|
696
+
697
+
1. Sign into [Power Automate](https://flow.microsoft.com/).
698
+
699
+
2. In the left pane, select **Solutions.** From the solution list, select **Regional Emergency Response Solution** to open the solution.
700
+
701
+
> [!div class="mx-imgBorder"]
702
+
> 
703
+
704
+
3. In the solution, filter on **Flow** to find the flows.
705
+
706
+
> [!div class="mx-imgBorder"]
707
+
> 
708
+
709
+
4. Select the **Portal User Request: Send Email on Decline Request** name to open the flow definition. Select **Edit** on the toolbar.
710
+
711
+
5. Specify the connection to connect to Common Data Service by selecting **Connections** and then either using the existing connection or using a new credential by selecting **Add new connection**.
6. After fixing the connection to connect to Common Data Service, select **IfRequestState ==**, and specify the user account that has a mailbox enabled account to send emails.
717
+
718
+
> [!div class="mx-imgBorder"]
719
+
> 
720
+
721
+
7. Select **Save** to save the changes, and then select **Turn On**.
722
+
723
+
8. Next, go to the flows list, and select the **Portal User Request: Send Email to Admins on Request Creation** name to open the flow definition. Select **Edit** on the command bar.
724
+
725
+
9. Fix the connection to connect to Common Data Service by selecting **Connections** and then either using the existing connection or using a new credential by selecting **Add new connection**.
726
+
727
+
10. After fixing the connection to connect to Common Data Service:
728
+
1. Select **IfRequestState ==**
729
+
2. Select **Connections** to specify the connection to connect to Common Data Service
730
+
3. Select **Connections** to specify the user account credentials that has a mailbox enabled account to send emails
731
+
732
+
> [!div class="mx-imgBorder"]
733
+
> 
734
+
735
+
11. In **Send an email**, ensure that you fix the URL as per your portal URL. For example, in this case, change rer6 to your URL value.
736
+
737
+
> [!div class="mx-imgBorder"]
738
+
> 
739
+
740
+
12. Select **Save** to save the changes, and then select **Turn On**.
741
+
742
+
## Step 15: Share admin app with other admin users
688
743
689
744
For your business admin users to use the admin app (model-driven app) to enter and manage data, it must be shared with them. It's easier to use Azure AD groups to easily share apps with a group of admin users.
Copy file name to clipboardExpand all lines: powerapps-docs/sample-apps/regional-emergency-response/includes/cc-getting-started.md
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,23 @@
1
1
## Getting started with the portal
2
2
3
-
When you visit the portal, you have an option to log in, or for the first time, redeem an invitation:
3
+
When you visit the portal, you have an option to sign in, or for the first time, request access:
4
+
5
+

6
+
7
+
Select **Sign In** when you already have signing credentials. Select **Redeem Invitation** if you'd like to redeem an invitation. You can also choose to request access using the **Request** option if you don't have an account alread.
Enter your first and last names, email address and mobile phone to request access to the portal. To select the parent organization, use the search icon and then select the parent organization or search as appropriate.
14
+
15
+
You can select a role when you request access. The **Parent Organization Administrator** role lets you manage administrative tasks. **Organizational HealthCare Worker** role allows you to submit healthcare related information. And **Report Viewer** role is used to view various dashboards using the Regional Government Emergency Response and Monitoring portal. For more information about roles, go to **Users** section in **Administrative Tasks**.
16
+
17
+
After you submit your access request, you'll receive an acknowledgement on portal and you'll receive an email once your access request is processed.
0 commit comments