• Replies 2 replies
  • Subscribers 336 subscribers
  • Views 37 views
  • Users 0 members are here
Related

Best Practice of Control Groups for consortium

Richard Comito
$organization

Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

We are looking at becoming a consortium.  So I am in the process of cleaning up our security and control groups.  The way things are set up right now is that we have Control Groups for Accounting, Marketing, Development, ect…  This has worked out fine when it was just the LA Opera.  However, after doing some reading and watching some old Webinars.  I am thinking that this process would not be the best way to move forward.

What I would like to know is what would be the best practice of Control Groups.   Do I want to keep the structure the way it is and only add in more description to each group to separate from the two organizations, or do I want to change the control group structure to be only the two originations names then with the security groups limit who sees what?

Yes I do realize that the changing of the Control Groups will be a huge task.  But if I have to do the work I might as well do it right.

Thanks

  • Former Member
    Former Member $organization
    Hi Richard
    From our experience, maintaining your existing groups would be the way to go(with additional description - we just have a standard 3- or 2-letter abbreviation for each org which is added to the front of the description wherever it helps, including Control groups).
    We have six orgs in our consortium. We have one general cg for each org, one for each case where two of us need access to the same season (mostly where SOH and one of our partners are both selling the season), one for each sub-org group (like your setup) that has different access rules, and then some cg's that represent a very specific access, which is not org-dependant, and might be given to individual user groups across multipe orgs (eg access to a specific shared facility).
    One of the great strengths of the control-group idea, I think, is the way you can use it in such a flexible way to achieve subtle access control. I don't think you should put limits on how it's used.
    Although it can get complex to administer used like this, that follows a general principle of trading complexity of administration off against complexity for the user, which I like to try to follow.
    Ken McSwain
    +61 (0)418 659 360
    Sent from BlackBerry

    -----
    Original Message -----
    From: Tessitura Technical Forum
    To: Ken McSwain
    Sent: Wed Aug 26 02:55:56 2009
    Subject: [Tessitura Technical Forum] Best Practice of Control Groups for consortium

    Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

    We are looking at becoming a consortium. So I am in the process of cleaning up our security and control groups. The way things are set up right now is that we have Control Groups for Accounting, Marketing, Development, ect… This has worked out fine when it was just the LA Opera. However, after doing some reading and watching some old Webinars. I am thinking that this process would not be the best way to move forward.

    What I would like to know is what would be the best practice of Control Groups. Do I want to keep the structure the way it is and only add in more description to each group to separate from the two organizations, or do I want to change the control group structure to be only the two originations names then with the security groups limit who sees what?

    Yes I do realize that the changing of the Control Groups will be a huge task. But if I have to do the work I might as well do it right.

    Thanks




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
    Please consider the environment before printing this email.
    =====This message is intended for the addressee(s) named and may contain confidential information.
    If you are not the intended recipient, please delete it and notify the sender.
    Views expressed in this email are those of the individual sender and are not necessarily the views of the Sydney Opera House Trust=====
  • $organization in reply to Former Member

    Ken,

    Thanks for your reply.  This really helps.

    Rich