1. 

   maron, Member

   Hi.

   It would be very helpful to have users who can edit some reports, and even create within a specific directory - which could then be deployed by an admin by moving it out of the directory. I foresee this as an additonal field in the mydbr_reports_priv with access_type or something similar.

   Right now we have over 100 reports, with some reports whom we do not want to share with all report creators etc.

   I realise once they have editing rights they can pretty much access the whole database, however the case is more being sure that older reports are not being edited, the best programmers also tend to have an overly curious nature while we want them to focus on the immediate tasks at hand.

   Regards,
   Maron
2. 

   myDBR Team, Key Master

   As you pointed out, with report creation rights comes the access rights to the reporting database meaning there is no way of limiting access in single installation just to specific directories.

   If you have multiple developers, what you can do is to set a separate reporting environments (development / staging / production) for the report creation process. Admin can then control which reports are visible to whom.

   --
   myDBR Team
3. 

   maron, Member

   Wouldn't this require 3 different installations?
4. 

   myDBR Team, Key Master

   That depends on your development process. If you want to limit access to reports you can do with two (development and production). Some have separate installations for staging as well.

   --
   myDBR Team

Reply

You must log in to post.