Best Practice - Running QStudio reports

[SueC]

My users are just now starting to develop and save Query Studio reports. 

What have you all found to be your best practice/strategy for having them save the query so that other users (non QS licensed users, just consumers) can run or view the report?

Thanks.

Sue

[CoginAustin]

I always had a common folder for departments that everyone in the department had access to, a division wide folder that everyone had access to, and an executive folder where only certain high level execs had access to.

I likened it to a shared folder on the network where people dropped things off and others picked it up at their leisure.

[SueC]

How did you save the queries so that others could run and view them?  As a report view?

Thanks.

Sue

[CoginAustin]

You can save the report, report view, sometimes a shortcut(if the user has access to where it points), or the generated report itself

[SueC]

That's what I thought but when I test it from a user account I either get a 'you don't have security rights' error or a 'soap fault' error.  I haven't dug into either error, assuming that it had to do with permissions or licensing.

But logically thinking (I know this is the burden I must carry in this life) I would expect to be able to write a query, save it and have any user be able to go to that folder and run it, providing they have access to that folder.  Are my assumptions wrong?

[CoginAustin]

Your report or view will take on the access of the folder it is located in. Assuming override permissions of parent is not checked.

Example:
I can create a QS report in My Folders. I can then create a Report View of this report in My folder. At that point the Admins and I can only see it. I can then move this report to our "Division Public" folder and everyone in the entire company has access to it because they all have read/execute permissions on the Divsion Public folder.

[SueC]

Then I must have something esle going on.  I'll have to dig into those errors a little more.  That's exactly what I'm doing.

Thanks.