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
+39-4Lines changed: 39 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -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 [add and manage portal users](#manage-portal-users) and **User Requests** to [view and manage portal user requests](#view-and-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
+
## View and 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, 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)
Copy file name to clipboardExpand all lines: powerapps-docs/sample-apps/regional-emergency-response/upgrade.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,19 +48,19 @@ On extracting the .zip file, you will see the following in the extracted folder:
48
48
|**Folder**|**Description**|
49
49
|---------|---------|
50
50
|**Package**| The folder contains the Package Deployer tool and the package that you will import later to set up the solution in your environment. |
51
-
|**Power BI Template**| Contains the Power BI Report template file (.pbit) that you will use to configure reporting. More information: [Step 5: Configure and publish Power BI dashboard](#step-5-configure-and-publish-power-bi-dashboard)|
51
+
|**Power BI Template**| Contains the Power BI Report template file (.pbit) that you will use to configure reporting. More information: [Step 3: Publish the latest Power BI dashboard](#step-3-publish-the-latest-power-bi-dashboard)|
52
52
|**SampleData**| Contains the sample master data files (.xlsx) that you can use to import sample data. |
53
53
54
54
## Step 2: Install the upgrade package
55
55
56
56
Install the upgrade package in the **same environment** where you have the
57
57
existing solution installed. You can install the upgrade package in one of the following 3 ways just like you did when deploying the solution for the **first time**.
58
58
59
-
- Microsoft AppSource (for Power Apps US Govt customers only). See [Option A: Install the app from Microsoft AppSource (US Govt customers)](#option-a-install-the-app-from-microsoft-appsource-us-govt-customers) in the deployment topic
59
+
- Microsoft AppSource (for Power Apps US Govt customers only). See [Option A: Install the app from Microsoft AppSource (US Govt customers)](deploy.md#option-a-install-the-app-from-microsoft-appsource-us-govt-customers) in the deployment topic
60
60
61
-
- Microsoft AppSource (for Power Apps commercial version customers). See [Option B: Install the app from Microsoft AppSource](#option-b-install-the-app-from-microsoft-appsource) in the deployment topic
61
+
- Microsoft AppSource (for Power Apps commercial version customers). See [Option B: Install the app from Microsoft AppSource](deploy.md#option-b-install-the-app-from-microsoft-appsource) in the deployment topic
62
62
63
-
- Deployment package that you downloaded earlier. See [Option C: Install the app from the deployment package](#option-c-install-the-app-from-the-deployment-package) in the deployment topic
63
+
- Deployment package that you downloaded earlier. See [Option C: Install the app from the deployment package](deploy.md#option-c-install-the-app-from-the-deployment-package) in the deployment topic
0 commit comments