Is partial disabling of interface possible? Need backend but want to lock down CP website
Summary:
How can we use the backend of an interface (the chat-inlay, mailbox, & message templates) in an interface for branding purposes, but prevent the customer from accessing the customer facing portion?
Content (please ensure you mask any confidential information):
One of our teams has drastically different needs and branding than the rest of our teams. While they are integrated into our system for the purpose of incident and chat handling, due to their other needs their primary website is external. We've updated the Oracle message templates and put their incidents in their interface mailbox for branding purposes. We also have a simple redirect on the main page that transfers users to their actual website. We've been getting an unexpected amount of session hits for an interface that technically does not need to be "user facing" active. We're still researching