Hi All,
We have a requirement like, we need to create a SecurityContext file that allows view access to review specific reports and specific review results for the user. Could you please let me know how it can be acheived to view only particular review and report using the security context file
Regards,
Devani N
For reports, consider configuring the users either in the Run Report or View Report Results sections
For reviews, consider configuring the users as monitors with Read access
For additional information on security context I suggest you watch the following videos:
Explaining Aveksa Security Entitlements (SecurityContext.csv file)
I have a very similar issue. In my case, we have two kinds of monitors. One kind needs read access (and only read access) and the other kind needs admin. The GUI only allows one access type for all monitors for the review.
As I began this reply, I realized that it is possible to use a coverage file to specify review monitors. The built-in help (YOUR_G&L_URL/aveksa/help/Launch_Help.htm#User_Tasks/Coverage_Files_Overview.htm) states pretty clearly that this kind of access can be set up using a coverage file. Can you confirm that it will work?
Haven't used a coverage file for monitors, but I have to assign reviewers, so I would expect it to work in the same way. No reason not to.
On the report front (i.e. normal IMG reports, not reviews or review results) we have used the security files to achieve selected access to selected reports.
While you can edit each report to allow users access that can be an admin overhead, certainly the more reports involved. The custom security route does require you have to consider both ends of the equation, i.e. how you identify the users AND the reports.
In our case we already have custom IMG app-roles for specific areas within the business so that covers the first part. For the reports we have two sets of "restricted" reports so simply configured a custom attribute on the report object and gave it a particular classification value. We then included a test on that value to create a custom IMG entitlement which was then included in the relevant custom IMG app-role(s).
For reports, consider configuring the users either in the Run Report or View Report Results sections
For reviews, consider configuring the users as monitors with Read access
For additional information on security context I suggest you watch the following videos:
Explaining Aveksa Security Entitlements (SecurityContext.csv file)
Creating custom aveksa entitlements