I think it depends on how many users you're going to have. If there
will be hundreds and hundreds per group/organization, then maybe
seperate instances. We have hundreds of users, but no more than 70 for
one particular group/organization, so we just create different queues
for the different support organizations and they all have their own set
of Queue managers (AdminCc Watcher) which (are the only users that) have
the rights to set up their own procedures, protocols, privileges, and
scrips/templates. We also have our own version of Approvals, which we
believe is a bit simpler than RT/Approvals/Workflow.
Another thing to consider is the technical support would be multiplied
by how many instances you have, as well.
LBNLOn 3/4/2009 10:13 AM, Steve OBrien wrote:
We are a regional service provider and have started using RT for our
internal users. We would like to be able to offer the service to other
entities and I was wondering what ways people have configured RT to meet
that need. Do you just create separate queues, or do you create
separate RT instances, or ???.
Community help: http://wiki.bestpractical.com
Commercial support: email@example.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com