Hopefully this isn't so open a question that it begs for "tough love" responses.
My company has just ended the selection process and we are starting with QlikView. Actually we started about 4 months ago on trial license and Personal Editions while the procurement group caught up. We anticipate this growing out like wild fire and have just installed the QV server hardware something like 40 cores and 256GB RAM. I'm not directly responsible for the program, but have a lot of enterprise IT experience and am worried that this may get out of hand like I've seen with SharePoint (sites not consistent, too many administrators, no controls...). I think that this is an awesome product and don't want to see a mistake early on cause it to get a black eye.
I've read through a number of posts and documents including many by John Callan. I have been through training (Dev and Designer). I setup QV Publisher and have several documents like the MetaScanner/Monitor, QlikView Ops Monitor, QVSystemMonitor_v3.2, and a couple of others reloading on schedule. That seems like a good start on the server monitoring outside of what our IT server admins do. Now I really want to get the development lifecycle documented.
One of my biggest concerns is controlling the data presented by dashboards. I have concerns that QVWs will be proxies to sensitive information like payroll data. If I have access to the whole general ledger and went through our existing process to gain that access, I could then publish a QVW that effectively bypasses that intial controled access procedure. On top of that, I could chain QVWs (and QVDs) together in such a way that it would require some effort to trace back the data to the source to determine the allowable audience. Currently, I will be proposing a series of documentation to be completed by the developer (and probably included on a standardized script tab) that explains the interfaces, data sources, data source owners, and intended audience. This is not fleshed out yet, but is primarily in my head. I am going to propose that a consultant be brought in to help get things started, but I don't know if we will get buy off on that considering the amount of money we just spent (I know, seems penny wise/pound foolish).
So, without asking for details (unless you are willing to share of course), generally, what are people doing to control this data proxy issue?