Is there a way we can control group or otherwise prevent a particular user from seeing various info in the header? We have customized data in the header and we didn’t want a licensee looking at some of the info displayed.
So how does Tessitura know which header to use based on security? How do you set it up?
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Amanda Freeman Sent: Tuesday, September 21, 2010 4:28 PM To: Robert Martin Subject: Re: [Tessitura Technical Forum] Const. Header
You could just have a different custom header, minus that info, for the security group containing the users in question. You could also change the visibility based on the current users user group, but it might be easier to just have different headers.
From: Robert Martin <bounce-robertmartin8728@tessituranetwork.com> Sent: 9/21/2010 3:33:59 PM
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!
Robert -
When you set up a login group in the security module there's a drop down field for 'Header Format'. This pulls any entry in your t_format_info file with a Gooesoft Report ID of Constituent Header. You can define what header someone gets by what login group they use.
HTH,
Heather
What groups see which header is configured in the security application. So if you're already using a custom header, you should see that set on your user groups there. It knows which header to display based on the security group the person logged in with.
If what you want is ALL the custom stuff hidden from a particular security group, you could just set that group, or all groups in a certain control group, back to use the standard header and you'd be done. If it's only some of the custom stuff but not all, you'd be better suited making a second custom header that omits only the part you don't want them to see. Either way, who gets what header is set in the security application.