Aellament Addresses Security
I’ve been dealing with Security all today, here’s well timed article on the part of Aellament.
It’s very similar to what I set up for my project…however, here’s the problem I’m dealing with, and I can’t figure out how to deal with it.
Here’s the scenario:
So I have a user that needs access to Account Detail information for one Project, but Account Summary for the other two…
I’ve been messing with 2 security groups…one for access specifically to Project 1 (detail), and the other to all Projects, with a Bottom Range of “Account Summary”. I just can’t get it to work. This is how I want it to present.
| Account Summary | Account Detail | Project 1 | Project 2 | Project 3 |
| Expense | Salary | $1000 | $1500 | $1000 |
|---|---|---|---|---|
| Equipment | $200 | $1500 | $1000 | |
| Supplies | $100 | $1500 | $1000 | |
| Total | $1300 | $1500 | $1000 | |
The problem is, it doesn’t apply the Bottom Range to Project 2 and 3…it will always be detail. Am I looking for some wonder metric that reacts differently based on attributes?
Interesting problem. Not sure if this would work for you but have you tried creating an aggregate at the Account Summary level and then putting a security filter on that table? You would probably need to create separate attributes to handle security for each table so that you can select different projects. For example create a security filter on Account Detail for Project 1 with an attribute called “Account Detail Project Security”. Then create a security filter on project 2 and 3 on the Aggregate table with an attribute defined as “Account Summary Project Security”. The next step would be to create two metrics that map to each table since I don’t think one metric could handle the query. Take each of the two metrics and add them together to create a third compound metric. The only issue you would then have to deal with is the join of Account Summary with Account Detail on the final query in which you are repeating the same Account Summary values for each of the Account Details listed. Hope this make sense.
Makes sense…just sounds like a pain in the butt.
This solution definitely requires some serious security filter maintenance, because the first time you have that accidental access to both then you’re doubling up the data. Know what I mean…
But, if it’s the way to go, then it’s the way to go.
Hmm bottom range should work. Try setting up a hierarchy object reflecting the relationship in the project. Also, can you post the actual results your seeing?