Admin Pages

General Helpdesk Settings

Adjust the helpdesk app settings and click "save changes" button.

Design Settings

  • Header background color - allows setting the top bar color. Dark color is highly recommended for a nice-looking design and for the gradient filling to stay visible.
  • Menu background color - menu bar color. No special notes.
  • Logo image - custom logo image. PNG format is required. Transparent background is highly recommended for a nice look. The image should be 60 pixels height (if larger - it will be resized, and this may not look good).
  • Favicon image - custom logo image. PNG format is required. Transparent background is highly recommended. The image should be 32 x 32 pixels.
  • DARK THEME - you can also enable dark theme UI on a "per-user" basis, just open you helpdesk user profile and enable "Dark UI theme"

Advanced Design settings: JavaScript and CSS

  • Custom CSS - this CSS code will be added to every helpdesk page. Be careful, changing CSS may lead to bugs and glitches.
  • Custom JavaScript - this JavaScript code will be added to every helpdesk page. Be careful, changing JS may lead to bugs and glitches.
  • KB-specific CSS - any extra CSS you want to add to your KB pages (all pages) along with the "global" custom CSS (see above).
  • KB-specific JS - any scripts you want to insert into KB pages. This can be Google analytics code or something like that.

General settings

  • Helpdesk URL (on-premise version only) - outgoing email notifications for ticket events contain a hyperlink to the ticket. The URL is initialized from the first request to the app. To change the URL, update this setting.
  • Helpdesk title - this name will show on top of every page in the application.
  • Title link - by default, top-left title (and logo) links to the ticketing system main screen. You might want it to link to your own website - set it here. And don't forget the "http://" prefix.
  • Note on the ticket creation page - the message will be displayed on top of the "new ticket" page. You can put some extra instructions or something similar into it. HTML allowed.
  • Helpdesk URL - (hosted version only) this is the "xxx.jitbit.com" address you want to use.
  • Helpdesk custom domain URL - (hosted version only) if you want to use a custom domain - set it up here. Then follow these instructions.
  • Hide "system" entries by default - Hide system comments like 'ticket has been assigned' or 'automation rule processed' etc. You can always unihde them by clicking 'More - show system entries' on the ticket page

Regional Settings

  • Language - specify the UI language for the app here. The system will also try to use the selected country's public holidays when calculating timing in reports (like "response time" etc.) but only if you set "working hours".
  • Time zone - specify your time zone, unless you want the helpdesk app to use default sever time.
  • Working hours - specify the working hours range (like "9 to 5"). This is used for reports, to calculate "durations" (i.e. how many hours spent on a ticket etc). You can leave this blank.

Various Settings

  • Restrict ticket deletion to Admins only - allows ticket deletion to Administrators ONLY. Turn it off to allow users to delete their own tickets.

  • Restrict ticket closing to Technicians only - Turn it off to allow users to close their own tickets

  • Disable avatars - do not use avatars with user profiles.

  • Auto-assign the first replying technician as ticket-agent - the first technician who replies to a "new" unassigned ticket becomes the "assigned" technician and the ticket automatically moves to "in-progress".

  • Allow assigning multiple techs to one ticket - allows you add "secondary assignees" to a ticket. The ticket will still have ONE main assignee, but you can add one or more "secondary" techs who help him. Being a secondary assignee allows seeing the ticket in "assigned to me" list, but that's it.

  • Allow users from the same company to see each other's tickets - every user profile has a "company" field. This option allows users from the same "company" to see each other's tickets.

  • Disable automatic 'time spent' clock on the ticket page - every time a technicians looks at a ticket in the web-application - the automatic timer tracks the time, the ticket has been open. This field can be edited manually as well.

  • Default category - this category will be preselected by default on the "new ticket" page. A user can then change it.

  • Auto-close inactive tickets after X days - if a ticket awaits an update from a customer, and the customer hasn't replied in X days - the ticket closes automatically.

  • Auto-delete closed tickets after X days - automatically delete (purge) closed tickets after X days (for example if you need to purge the old tickets for compliance reasons).

  • Reopen closed tickets on new replies - Choose what happens to a ticket when a new reply from a customer comes after the ticket has been closed:

    • Yes - always reopen tickets on new replies
    • No - keep tickets closed no matter what happens (not recommended)
    • Within days - only reopen if a ticket was closed within X days. If a new reply comes after the set number of days a new ticket will be created.

Knowledge Base Settings

  • KB description - the "title" text for your Knowledge base. It is shown on the KB homepage, on the top. You can use HTML.
  • Allow unregistered users access the Knowledge Base - makes the Knowledge Base accessible to guests.
  • Ideas forum - enable or disable the "Ideas forum" where users can submit and vote for new features.

Assets settings

  • Disable "assets" - completely hide the asset management module.
  • Restrict asset management to Administrators only - this will allow technicians to add/remove assets to tickets, but editing and viewing available assets will be restricted to Administrators only.

Authentication Settings

  • Shared secret for remote authentication - if you want to utilize the helpdesk's "remote authentication API" on your website or application, specify the shared key here. When you redirect your authenticated users to the helpdesk, use this link format: http://HelpdeskUrl/User/AutoLogin?username=xxx&email=yyy&userHash=HASH&new_ticket=1 where HASH is calculated as follows: MD5(name + email + shared-secret + dd + mm), "dd" and "mm" being current day and month (2 digits).

    If the user account does not yet exist in the helpdesk system it will be created automatically. Read more here also try our autologin builder that is linked below this setting.

    As you can see you can optionally pass the "new_ticket" parameter that will redirect a user to the ticket submission form right after he has been "auto-authenticated" by the helpdesk.

    This setting is also used as an encryption key and salt for many modules throughout the app - for "reset-password" codes, publicly shared ticket URLs etc.

  • Allow unregistered users submit tickets without logging in - allows unregistered users to submit new tickets right from the login page, without registering.

  • Allow new users to register themselves - shows a "register now" sign-up link to a user, who has no account yet. Turn this option OFF if you want to add all new users manually.

  • Allow users to edit their username and email - you can disable this option, so users do not change their username accidentally.

  • Disable "remember me" - disallow perpetual logins, recommended for HIPAA compliance.

  • Require 2FA authenticaiton - enforce 2-factor authentication for all users. All user who haven't set up their 2FA device will be prompted for 2FA setup when they open any page in the app.

  • Enable 'login with Google' - allows user log in with their Google account.

  • Remote login URL - when a user tries to login into the helpdesk app - you can redirect him to a custom login URL (at your site or a web-app) where you would authenticate the user and then send him back to the helpdesk app. If you accidentally set a faulty login URL - simply open the default login page with a "noredirect" parameter, like this "/User/Login?noredirect=1"

  • Enable SAML 2.0 single sign on - you can enable single sign-on with a SAML-provider (like OneLogin for example)

  • Redirect users to the idendity provider automatically when SAML enabled will automatically redirect everyone to SAML provider. Use noredirect=1 to rpevent this

  • Hide regular 'username/password' inputs from the login page when Google or SAML enabled - leaves only the "SAML LOGIN" button visible. Sse ?showlogin=1 to see the user & password inpuits again

Previous
Admin main page