Implementing new Users with specific rights but NOT consortium

Hi,

We manage the ticketing and e-commerce for several other theatre organizations in the Boston area.  It's a service that comes standard when they rent our space.  The nice thing is, we get our hands on their patron data  for prospecting and they don't need to worry about the e-commerce and expense side of presenting.  We however, have never allowed these groups permission to actually use Tessitura, but we would like to explore providing them with more accurate and "on the go" reporting.  One particular theatre group has become quite large over the past few years and we would like to provide them with easier access to their data.

Using the large group as an example, and since we don't want to create an actual consortium environment in Tessitura, the easiest solution I can think of is to create a unique User Group and Control Group for that large group and provide them with the data they can access. I can't, however, seem to figure out how to restrict OUR data from their viewing or reporting. For example, in the standard SSRS Report- Performance Seating Book, they are still provided the options to see our seasons and therefore could report on this patron data.  Do I have to build the filter into the SSRS report template somehow and thereby create a separate report so they cannot see the other offerings? 

Does anyone have any other suggestions to filter out data so they can only see their patrons?  Is that possible without taking the plunge and splitting off everything and being a consortium?  Any resources on this would be helpful!  Thanks! :)

Parents
  • Hi Tiffany,

     

    We are a consortium, but we are also doing something similar to what you are describing with two companies outside of our consortium. If the company’s seasons are tied to the new control group you created and the security group only has access that one control group, people using that security group should only see the appropriate seasons. (As a side note, it’s also important to add that new control group to other security groups that should see those seasons; otherwise, once you change the control group of the season, those other users will lose access.)

     

    To confirm, I just tested this in our environment, and the Season drop-down of the Performance Seating Book report only presented applicable seasons based on the control group(s) the current security group has access to. 

     

    There may be other things to consider in regards to security – it depends on what security objects and other reports you are granting them access to.

     

    I hope that helps…

     

    Thanks,

    David

     

Reply
  • Hi Tiffany,

     

    We are a consortium, but we are also doing something similar to what you are describing with two companies outside of our consortium. If the company’s seasons are tied to the new control group you created and the security group only has access that one control group, people using that security group should only see the appropriate seasons. (As a side note, it’s also important to add that new control group to other security groups that should see those seasons; otherwise, once you change the control group of the season, those other users will lose access.)

     

    To confirm, I just tested this in our environment, and the Season drop-down of the Performance Seating Book report only presented applicable seasons based on the control group(s) the current security group has access to. 

     

    There may be other things to consider in regards to security – it depends on what security objects and other reports you are granting them access to.

     

    I hope that helps…

     

    Thanks,

    David

     

Children
No Data