Changes for page Shared Reports and Report Subscriptions

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.karimpirani
	1	+XWiki.sghareeb

Content

...	...	@@ -1,12 +1,12 @@
1		-Shared Reports gives an organization the capability to create consistent reporting and analytics across an organization or across various programs within the organization. The Admin User can create Master Reports that will be "shared' across OUs; the report can be run be those that the report has been shared with; however, the report will only show data relevant to that user's information based on their roles, responsibilities and permissions, across their clients and OUs. Let's look at an example to clarify.
	1	+Shared Reports gives an organization the capability to create consistent reporting and analytics across an organization or across various programs within the organization. The Admin User can create Master Reports that will be "shared' across OUs; the report can be run be those that the report has been shared with, however, the report will only show data relevant to that user's information based on their roles, responsibilities and permissions, across their clients and OUs. Let's look at an example to clarify.
2	2
3	3
4	4	For the purposes of this Shared Reports example, we will use the Outcomes Snapshot Report across all OUs in this organization.
5	5
6	6
7		-The Admin User first sets up the report, just as they would any other report, with 2 exceptions/additions. Basically, the 3 main items are:
	7	+The Admin User first sets up the report, just as they would any other report, with 2 exceptions/additions. Basically the 3 main items are:
8	8
9		-1. Create the report as it is desired to have everyone run it. It will be the same report for all users, but with the added element that the report will only be run for the OUs, staff and clients that each user who runs this "Shared is responsible for and has access to view for everyone else that runs this "Shared Report." Basically, they will only see what they have responsibilities for when they run the report for themselves.
	9	+1. Create the report as it is desired to have everyone run it. It will be the same report for all users with the added element that the report will only be run for the OUs, staff and clients they are responsible for and have access to view for everyone else that runs this "Shared Report." Basically, they will only see what they have responsibilities for when they run the report for themselves.
10	10	1. The **OUs** overall should be selected for this report. The Admin User will often select all OUs and let the report break it down for each staff user running the report. The Admin User can also create this report just for a specific set of OUs, possibly in a situation where the report would only apply to those specific OUs for any reason.
11	11	1. The **Shared Roles** need to be selected. This selection determines what Staff User Roles will have this report shared with them to run.
12	12
...	...	@@ -63,7 +63,7 @@
63	63
64	64
65	65
66		-[[image:Shared Reports - Note - User only sees their OU.png||width="35%"]]
	66	+[[image:Shared Reports - Note - User only sees their OU.png||width="50%"]]
67	67
68	68	Below is an example of the Outcome Snapshot Report for a specific user. It will be customized for each Staff user that runs the report based on their responsibllies and persmissions as mentioned above, yet has the same consistent report logic for all.
69	69