UNKNOWN System -> Multiple deployable front ends to connect to one backend

[mjormakka]

We would like to be able to easily develop customer specific helpdesk front-ends to our single help desk back-end. By back-end I mean a full featured installation of a Kayako (eSupport) and a single database running at www.support.com. This back-end is used by our staff to set up all SLAs, departments and other settings common to all our support services.

By front-end I mean a heavily customized Kayako eSupport instance that runs for example at a subdomain customer.support.com (i.e. no staff or admin panels etc.) and is connected to the one single database at www.support.com. I.e. all Kayako instances would use the same database.

Currently this is not possible because there are instance specific information stored at the database, especially Product URL. And the only way to implement a customer specific "front-end" is to play around with templates.


Therefore I request that all this instance specific data is moved to property files instead of the database.

[runderwoodcr]

I agree with mjormakka, the ability to manage multiple front ends from one single backend is a great feature, I know that there are a lot of Support Suite users that offer support services, and is really hard to have a customization for every customer, besides that there have to be a ghost copy to try to emulate a single backend, so in my opinion this is not just a good to have, is a need, talking in my own experience I've been configuring Kayako from version 2, and this feature will save a lot off development time and debugging time.
One Single DB and Administration area with multiple frontends/interfaces is really a need.