In my experience, the rules for groups are driven by business logic rather than computational ease. That is, there are rules somewhere that determine who can see what and these rules can be based on law, position in the company, clearance level, or personal preference of the rule-maker.

If your concern is for performance, I wouldn't worry too much until you see the performance problem manifest itself. I've worked on systems that were simple user->access thing before that scaled pretty well. (Caveat: these were on fairly large hardware.) I think you may have some space before you hit a wall.

If your concern is maintenance, I think maintenance is easier if the maintainer can hang the group on something tangible. For example, the Accounting example provided above. I think it would be very difficult to maintain groups based on some optimization paradigm. In fact, you would probably need to re-group over time as people moved around and the landscape changed.

I'm not aware of any common solutions to the problem. My guess is that it's because the solution is often specific to an organization. So if you hit the performance wall, you may need to work with the people who decide on report access and determine how people can be grouped more efficiently.

In reply to Re: Deducing Ideal Groups by cbrandtbuffalo
in thread Deducing Ideal Groups by pboin

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.