Restrict login using a sql database containing usernames and passwords
Currently anyone can create a ticket
-
Jim commented
The ability for customers to easily see all their past ticket history is critical. Requiring a registration with un/pw seems to be the only way to do that.
-
Chris Marsh commented
Yes I would have to agree this feature would be most useful; as we already have the ability to create users, assign them passwords and limit the categories that they can view.
It would be useful to extend this usage to the root page so that users could be forced to login via a switch in the settings and then they could only log tickets against their categories; in fact it would be ideal if they couldn't even see categories not assigned to them.
Best Regards......
-
RUss commented
I'm surprised this isn't already a feature.. I want to give each client a login where they can create tickets, and view their tickets (filtered by status).
I don't want Dick, Tom or Harry creating tickets either..
This is a must-have surely? Ca't see how it practically useful any other way.. -
Anonymous commented
We have installed HESK into our intranet. It would be great if the username field and email address could self populate from the staff member's profile (login) to the intranet.
-
Michael Hiatt commented
We require no accounts to deal with. The security question is sufficient. If implemented, please make as an option!
-
Donut Seller commented
Please make this optional. Make it say something with: "Do you want to register? If so, you can see all your submitted tickets.", and make it totally optional whether the customer wants to register or not.
-
Arturo commented
+3 here. With the login feature it would be possible to a customer to see all his tickets and their progress in a single page.
I think that this feature would be quite useful from the customers perspective. -
Yasawas commented
+1 here. Fully agree with Christine on this implementation.
-
Boyce commented
We use this on an internal site, if the users have to log in, that will be a significant impediment to their willingness to use the helpdesk system. OTOH if I put this on my personal site, I don't want anonymous submissions. I'd suggest an admin option: A) All All Anonymous B) Allow password secured [with hint] C) require confirmed email address
-
jimmy commented
+1 on this.
i need registered user to input ticket.
im using few admins to input ticket and i need to know which person input each ticket. -
alka commented
Add it in such a way that you can specify email and password column in such way that you can use a membership sites database for user authentication that would be awesome.
-
Christine commented
Rather make this optional. Right now, we love the no login option, but of course there may be sensitive area's you only want certain groups of users to view who are not staff members.
-
Ed commented
+1 here. I plan on testing Hesk with our customers. I don't want any person off the street being able to "play games" or submit a ticket for work they don't intend to pay for. I know I can filter them manually but it's time I don't have being a one man shop right now.
If you plan to implement this, then I suggest having one "superuser" such as the owner of the business being able to see what tickets his/her employees have created and their status. Like groups for customers. This would necessitate a db change but maybe something you could work on in the future.
-
Neil commented
+1 here too. It is very important for this kind of system to uniquely have tickets associated to one customer and only he can see them by using his login. Much better also if the ticket numbers could be sequential, we find that easier to handle than something like U7ZYPHZU58
-
Henrique commented
+1 Here. We are a governamental institution using Hesk to our helpdesk service but since we don't want everybody to create a new ticket we have to "hide" the create ticket from our customers and only share it with our team (that hear the complains and fill the tickets).
-
Paul Laufer commented
+1 for this one. I need to be able to secure the site from internet background radiation. We only want our customers logging in.