How can I have read only reports that are accessible to everyone, but only the admin has full access to modify?
18 December, 2012
Support,
I would like to be able to produce reports that reside in an unsecured folder but are secured as read-only save for users with the admin role or some other identifying feature. For everybody else, it would be possible to view and copy a version of the report for editing, but for all purposes the original report would be left unmolested and in its original state.
The purpose behind this is to retain an original version of the reports we're constructing for our clients within Yellowfin, even if our clients ultimately choose to modify that report somehow. This will help us when identifying support requests, e.g., if a client breaks a report that was delivered to them and then altered somehow, this may in fact be billable rather than a support task. It goes without saying that this would help us to identify why something broke, as well.
Is it possible to implement something like this? I've been fishing around the forum and wiki, and it doesn't seem like anything fits the bill here.
Thanks
I would like to be able to produce reports that reside in an unsecured folder but are secured as read-only save for users with the admin role or some other identifying feature. For everybody else, it would be possible to view and copy a version of the report for editing, but for all purposes the original report would be left unmolested and in its original state.
The purpose behind this is to retain an original version of the reports we're constructing for our clients within Yellowfin, even if our clients ultimately choose to modify that report somehow. This will help us when identifying support requests, e.g., if a client breaks a report that was delivered to them and then altered somehow, this may in fact be billable rather than a support task. It goes without saying that this would help us to identify why something broke, as well.
Is it possible to implement something like this? I've been fishing around the forum and wiki, and it doesn't seem like anything fits the bill here.
Thanks
Hi,
The easiest way around this is to create a report category that will be used to store the master (read-only) reports.
You would make this category secure and give delete access for admins, and read-only access for other users.
You would then have another report category that the users can save their reports into.
Here's an example, I have an admin user, and a group ('Customers')that contains other users.
I then make the sub-category 'Charts - Read only' secure with delete access for the admin, and read-only for my group:
Now when the admin user runs any reports from this category, they have full access and can modify existing reports.
However, users in the Customer group , only have the option to run or copy the report. Once they copy the report, they are then able to save it in another report category.
Additional information on setting up security can be found in the wiki Security Framework .
Please let me know if this doesn't give you the results you were after.
Regards,
David
The easiest way around this is to create a report category that will be used to store the master (read-only) reports.
You would make this category secure and give delete access for admins, and read-only access for other users.
You would then have another report category that the users can save their reports into.
Here's an example, I have an admin user, and a group ('Customers')that contains other users.
I then make the sub-category 'Charts - Read only' secure with delete access for the admin, and read-only for my group:
Now when the admin user runs any reports from this category, they have full access and can modify existing reports.
However, users in the Customer group , only have the option to run or copy the report. Once they copy the report, they are then able to save it in another report category.
Additional information on setting up security can be found in the wiki Security Framework .
Please let me know if this doesn't give you the results you were after.
Regards,
David