Knowledge base / Feature Requests / Restricting access to raise a ticket to users within a Google Apps domain [DONE]

Restricting access to raise a ticket to users within a Google Apps domain [DONE]

Submitted 7/27/2010 by admin

Is it possible that a feature is made in which only users from within the Google Apps domain can raise a ticket and they need to login to their Google Apps account to raise a ticket or if they are already logged in, using SSO they are logged into estreamdesk?

I'm an admin of an educational institute and would like to restrict the tickets raised to the users of my domain only.

Comments

AsistHogar Central

I agree. That's a very important issue. I found that anybody from any domain can register to my eStreamDesk (I hve it with Google Apps also), so it doesn't helps that knowledge base is restricted to logged in users if everybody can register and log in.

8/2/2010 7:46:26 AM -05:00

Jerry Mancuso

It would be nice to have more user control.

I figured out a way that we can restrict ticket management as we need.

  • Only Agents can view others' tickets, so the administrator would need to set all new registrants from your domain to an agent if they'll need to manage tickets.
  • I use Departments to keep tickets separated with users.
    • Only users of a specific Department can see tickets for that department, other than their own tickets.
  • I manage our "Support" Department, but I've also added a couple of others for specific departments like Operations or for specific offices.

I'm sure you will have too many users, but you may be able to set a Ticket Rule to restrict new tickets.  For instance, when a new ticket is created, if Ticket Requester is not listed, it'll be deleted (depending on how much of a problem this is for you) and an email can be sent to the requester explaining that the administrator is approving their ticket access.  You could also have it send an email to the administrator to add that user to the Ticket Rule.  As new users register, if approved by the administrator, that user can be added to the Ticket Rule so they will be able to submit tickets. Instead of deleting, you could just add a label for UNREGISTERED and priority LOW. [unverified] [This is assuming that the Ticket Rules run in the order they are listed under "Ticket Rules"]

First Rule:

  • Rule Name:
    • Registered Users
  • Rule Trigger:
    • Ticket is Created
  • Rule Conditions:
    • Ticket Requester > Equal To > (Add another condition for each approved user)
      • I'm not sure if these conditions are AND (inclusive of each other), or OR (exlusive of each other)
  • Rule Actions:
    • Add Label > Registered

Next Ticket Rule:

  • Rule Name:
    • Un-Registered Users
  • Rule Trigger:
    • Ticket is Created
  • Rule Conditions:
    • Ticket Labels > Doesn't Contain > Registered
  • Rule Actions:
    • Either Delete Ticket or Add Label > UnRegistered
    • Send Email to User > Requester
      • Explain they will have to wait 24-48 hrs (or whatever) to be registered on the site for Tickets
    • Send Email to User > (Whoever the Administrator is)
      • Alerting them of the ticket and that the user needs to be added to the Registered list
8/19/2010 4:27:22 PM -05:00

Support

This feature is now available! Thank you for your feedback.

9/7/2010 9:17:28 AM -05:00

Search