User Roles- Limit Report Writer to 'Create or Copy'

Hi Tony,

Thanks for reaching out with your question. I did some testing and came to the same conclusion as you; user roles do not provide the access granularity to "make a copy" but not "edit" unfortunately. However, there are other ways to accomplish this, and I believe your best option would be to leverage Yellowfin's Folder Security options.

As an administrator, you could create a Private Folder containing your report templates, and in turn create copies of the report templates in other locations with your desired access permissions. I've attached screenshots illustrating the process of creating and configuring a folder structure that would achieve the functionality you're looking for. Does this sound like a viable alternative to you?

Thanks,

Eric

So it sounds like as an Admin I would need to manage two sets of reports (the original, and the copies). The drawback to this approach is managing possibly two versions of the same report if changes/updates aren't applied to each individual report.

In the case where a user were to copy the 'template' report, they would then be able to modify this per their own requirements. If it were intended that such a report would be kept up-to-date with the template, the admin would have to manage all copies of said template. Hopefully this clarifies things for you.

Thanks,

Eric

Hi Tony,

Just wanted to check in on this issue; did you have any questions or want to push this forward as a possible enhancement?

Thanks,

Eric

Hi Tony,

I've converted this question to an Idea and submitted to our development team. Updates will be provided.

Thanks,

Eric

You can skip the two folder option. Create a public <Template> folder, set the permission to read with access given to the report writers. The Writers will be able to copy the report but will not be able to directly edit the <Template> reports. They also will not be given the opportunity to publish the report back to the <Templates> folder. This is true for Admins as well. They will not be able to edit the reports in the <Templates> folder unless they explicitly change the permissions on that folder. This is a good idea and I will use it in my implementation.

Hi Tony,

Just wanted to provide an update here, developers have marked this as enhancement as a "won't do:"

We don't have any plans to introduce this concept.

There may be some work arounds putting the "template" reports in a secure folder and only allowing other report writers to copy them (but not modify).

I will mark this ticket as "not planned" accordingly.

Regards,

Eric