Settings and activity
6 results found
-
1 vote
An error occurred while saving the comment -
3 votes
An error occurred while saving the comment 
Treblig
commented
-
527 votes
An error occurred while saving the comment Treblig
commented
See if my comments on https://hesk.uservoice.com/forums/69851-general/suggestions/994161-restrict-login-using-a-sql-database-containing-use or https://hesk.uservoice.com/forums/69851-general/suggestions/1083849-customer-database fit your needs (although for an old version of HESK)
Not a true "department" feature but rather a login for different organizations using the same HESK.
Treblig
supported this idea
·
-
297 votes
An error occurred while saving the comment Treblig
commented
In a very old version of Hesk V2 (probably 2.6.7 or 2.6.8 ), I had implemented a forced login for all users.
As far as I can remember all changes to Hesk files are those indicated in the text file below (link).
Users had to be pre-registered in the Hesk users table by the Hesk admin, there is no register form only a login form.
Whether these changed are transferable to other Hesk V2 / V3 versions or not is left as an exercise to the brave as I have changed jobs & company and no longer use Hesk.Warning & disclaimer : I'm not a "true" PHP developer and accept no responsibility whatsoever to changes anyone makes to Hesk
See https://developers.phpjunkyard.com/viewtopic.php?f=14&t=6639&p=28605#p28605
Treblig
An error occurred while saving the comment Treblig
commented
Hi,
New to Hesk, we're planning to use Hesk for multiple "companies/organizations/entreprises/whatever_you_want_to_call_them" and we made a few changes to Hesk :
1. only registered users are allowed to submit/change tickets : users are pre-registered in Hesk using hesk users table.
2. "categories" become "organizations" and registered users of organization A can only submit and see tickets of organization A. One user = one organization (except Hesk "root", i.e me !)
Changes are not a "one size fits all" type, especially if you need categories.
I'm playing with PHP and won't call myself a developer so I have probably left security holes.If anyone wants my changes to Hesk, please drop me a private message with your email (I may not follow this site regularly)
-
28 votes
An error occurred while saving the comment Treblig
commented
kind of same as "{{whatever_page}}" in mediawiki (wikipedia & all) ?
-
455 votes
An error occurred while saving the comment Treblig
commented
I just implemented a mandatory login to hesk (based on /admin/index.php).
I also use the category field to identify each entreprise/company/organization and each user is assigned to his/her company and can submit only tickets for that company.
The purpose was to have a unique hesk for several customers.Admins can still view and submit tickets for any company.
I'm using the hesk user table and each user must be pre-registered.
There is no facility where users can register themselves (didn't bother to do it since I have no use for it)
I can assign a status of "pseudo admin" to a specific user in a company by setting the "Manage users" option in their profile.
"pseudo admins" can then register users for their own company ONLY.
The registration of individual users doesn't have to be managed by the hesk "root admin" (though s/he can if need be).I haven't extensively tested everything (I first installed hesk less than a week ago) but it looks like I didn't break it all ;-)
1. I'm not a very experienced developer so I won't accept any responsability if there are security holes.
2. I'm setting a few cookies
3. admins have to login twice : first to access hesk (as any user), second to access the admin interface.
4. it won't fit everyone since hesk categories are used for another purpose.
5. don't even think of asking SSO or other improvements. I may correct bugs though.If interested let me know your email address.
Not sure there's private mail on this site. If there is, please use it rather than leaving emails in comments.
check here: https://hesk.uservoice.com/forums/69851-general/suggestions/994161-restrict-login-using-a-sql-database-containing-use