Hey everyone,
Have any of you given "read only" access to your web vendors (who aren't members of the ecosystem of partners) to Tessitura? Our web vendor is asking for access to understand ticketing setup (something I've never heard of in all my years of using Tessitura). If you are using a non-ecosystem web vendor, what access did you give to them to understand Tessitura and the API?
- Chris
First of all, I've typically worked with web vendors within the Tessitura ecosystem. My question to you is, would you give these folks read-only access to your system?
That then leads to the question, If a web vendor is under NDA with the network and with your organization.
What are your thoughts about not giving read access to Tessitura?
An argument could be made that giving them access would make them more productive in working with the API. Less backing and forth-ing about what the setup is and why the calls are or are not working.
I'm dealing with a similar situation at the moment and do not have a clear answer for myself. But, your question has gotten me thinking... Thanks.
My system administrator and I are of the mindset of not giving them access to the actual database. With patron account information much more easily accessible this way (even in read only as an access area might be missed), that opens up too much liability. In order to have access to the administrator sites for TNEW, all vendors have to sign an NDA (I believe this also has to be on-file to access the Developers Portal...which our vendor has access to as well).
My biggest concern with giving them access to the actual database is many fold. The first is, of course, safety of patron information (especially any accounts we have from UK patrons). I would imagine that any and all questions could be answered through the Slack channel for Developers as well as through the knowledge base in the Developers portal.
I would rather we use some money and purchase a consulting package to work through what really needs to be given or access to Developers versus just giving access willy-nilly.
It would also be nice if, during implementation, the TNEW consultant assigned to do implementation also spent time making sure web vendors have all the access they need to do work. It's not easy figuring out all the bits and pieces you have to do to get them access.
I'll +1 the idea:
Christopher Cuhel said:It would also be nice if, during implementation, the TNEW consultant assigned to do implementation also spent time making sure web vendors have all the access they need to do work. It's not easy figuring out all the bits and pieces you have to do to get them access.
Yeah, this is both in Tessitura Security, and things like SLACK, sandbox, developer portal.
I eventually reached out to a bunch of folks and eventually found these page: