Hi again!!
Let me explain you our need so that you can help me to decide how to organize the catalogues/portals
The situation is the following:
We need to be able to manage access to offices. Depending on which office the customer request access to, the ticket will be managed by one "Office team" or another independently.
Each "Office team" should only be able to see their tickets, if we have understood the operation of the tool correctly, we think that, the best option is to have separate portals to manage access to each office, however this has the problem that the number of portals will be very high (as many as offices). What can we do?
to summarize the conditions are:
Thank you very much in advance!!!
Hi @Andrea Dieguez ,
If I understand you're use case correctly here is what I recommend. First let me state that it appears to me that you will have different groups of agents supporting each physical office. Second, I have one fundamental question - do these "office teams" truly need to be restricted from seeing the requests other office teams. Could it be that the team needs to simply understand to watch their specific queues and not others? If they need to be truly restricted then I would likely recommend having separate projects for each office. The problem with this is that the customer will see a different project/portal for each office and that might not be ideal. If the restriction is not so severe then I would recommend a single project and simply set up the queues in this project based on offices which could be a custom field in your project. In this case each "office team" simply monitors their queue and ignores the others.
@Jack Brickey Indeed you answered my questions we will explain the team the situation but in any case you have already answered my question, I suppose that we will opt for different portals in any case, what has been said, thank you very much for the explanation!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.