Separate Product Catalogs for Teams?

Hello all,

I am looking into the best way to set up performances that are specific to different teams. An example is that would be education classes that only the Education Team sees, and film screening performances that only the Box Office team wouls see.

I know the obvious solution is to manage this through Mode Of Sale, but performances in non-active MOS are still visible, although coloured red and unable to be sold. I am fairly certain that these 'red' performances would also be funneled into our Hotlist for all users each day.

Has anyone experimented with using Security groups or some other method to completely hide performances from the Product Catalog calendar? I imagine this would be very useful for orgs with a large number of Performances each day, and have different sales teams.

Many thanks,

Nicholas

  • Hey Nicholas,

     

    I think Control Groups work well in this situation. J

     

    Beau.

     

    From: Nicholas Hudson-Ellis [mailto:bounce-nicholashudsonellis2615@tessituranetwork.com]
    Sent: Tuesday, 28 February 2012 13:30
    To: Beau Vigushin
    Subject: [Tessitura Ticketing Forum] Separate Product Catalogs for Teams?

     

    Hello all,

    I am looking into the best way to set up performances that are specific to different teams. An example is that would be education classes that only the Education Team sees, and film screening performances that only the Box Office team wouls see.

    I know the obvious solution is to manage this through Mode Of Sale, but performances in non-active MOS are still visible, although coloured red and unable to be sold. I am fairly certain that these 'red' performances would also be funneled into our Hotlist for all users each day.

    Has anyone experimented with using Security groups or some other method to completely hide performances from the Product Catalog calendar? I imagine this would be very useful for orgs with a large number of Performances each day, and have different sales teams.

    Many thanks,

    Nicholas



    --
    View this message online at http://www.tessituranetwork.com/COMMUNITY/forums/p/6738/21212.aspx#21212 or reply to this message
    --
    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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!

    DISCLAIMER:
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    This e-mail message may contain information which is confidential to the message originator.  If you have received this e-mail by mistake, please advise us immediately by return e-mail and delete this e-mail, including any attachments, from your system. You may not disclose, copy or distribute any part of this e-mail. Also, please note that the opinions expressed in this e-mail are those of the author, and are not necessarily those of the originators employer. Any concerns about the content of this email should be immediately directed to
    mail@melbournerecital.com.au.  This message and any attachments have been scanned for viruses prior to leaving the originators network.
     
    Please consider the environment before printing this email.

  • Former Member
    Former Member $organization

    Hi Nicholas

    The traditional way to absolutely control access to performances is via Seasons.

    If you put your performances into separate Seasons, and control-group the Seasons, then users without the relevant control group won’t see them at all.

     

    ________________________________
    Ken McSwain

    Systems and Technology Manager

    Australian Chamber Orchestra

     

    ken.mcswain@aco.com.au

    Ph   +61 2 8274 3833 ::  Mob +61 418 659 360 :: Fax  +61 2 8274 3801

    PO Box R21, Royal Exchange NSW 1225

    2 East Circular Quay, Sydney NSW 2000

     

    From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Nicholas Hudson-Ellis
    Sent: Tuesday, 28 February 2012 13:30
    To: Ken McSwain
    Subject: [Tessitura Ticketing Forum] Separate Product Catalogs for Teams?

     

    Hello all,

    I am looking into the best way to set up performances that are specific to different teams. An example is that would be education classes that only the Education Team sees, and film screening performances that only the Box Office team wouls see.

    I know the obvious solution is to manage this through Mode Of Sale, but performances in non-active MOS are still visible, although coloured red and unable to be sold. I am fairly certain that these 'red' performances would also be funneled into our Hotlist for all users each day.

    Has anyone experimented with using Security groups or some other method to completely hide performances from the Product Catalog calendar? I imagine this would be very useful for orgs with a large number of Performances each day, and have different sales teams.

    Many thanks,

    Nicholas




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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!


    Explore the 2012 season at aco.com.au/season2012

    This email is confidential. If you are not the intended recipient you must not disclose or use the information contained in it. If you have received this email in error please notify us immediately by return email and delete the document. The ACO is not responsible for any changes made to a document other than those made by the ACO or for the effect of the changes on the document's meaning. The ACO accepts no liability for any damage caused by this email or its attachments due to viruses interference, interception, corruption or unauthorised access.
  • Very elegant solution, Seasons/Control Groups. Thank you gentlemen!