<div><style>p { margin: 0; }span.fr-emoticon.fr-emoticon-img { background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle; } span.fr-emoticon { font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0; } blockquote { border-left: solid 2px #5e35b1; color: #5e35b1; margin-left:0; padding-left:5px;}blockquote blockquote{ border-color: #00bcd4; color: #00bcd4;}blockquote blockquote blockquote{ border-color: #43a047; color: #43a047;} table.grid{ border-collapse: collapse;} table.grid td, table.grid th { border: 1px solid #ddd;} .fr-fic.fr-dib{ display: block; margin: 5px auto;}.fr-fic.fr-dib.fr-fir{ text-align: right; margin: 5px 0 5px auto;}.fr-fic.fr-dib.fr-fil{ text-align: left; margin: 5px auto 5px 0;}.fr-fic.fr-dii{ float: none; margin: 5px auto;}.fr-fic.fr-dii.fr-fil{ float: left; margin: 5px auto;}.fr-fic.fr-dii.fr-fir{ float: right; margin: 5px auto;}img.fr-dib.fr-fir { margin-right: 0; text-align: right;}img.fr-dib.fr-fil { margin-left: 0; text-align: left;}img.fr-dib { margin: 5px auto; display: block; float: none;}img.fr-bordered { box-sizing: content-box; border: solid 5px #CCC;}img.fr-shadow { box-shadow: 10px 10px 5px 0px #cccccc;}img.fr-rounded { border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;}</style><p><strong>Configuration > Advanced Settings</strong></p></div>
<style>p { margin: 0; }span.fr-emoticon.fr-emoticon-img { background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle; } span.fr-emoticon { font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0; } blockquote { border-left: solid 2px #5e35b1; color: #5e35b1; margin-left:0; padding-left:5px;}blockquote blockquote{ border-color: #00bcd4; color: #00bcd4;}blockquote blockquote blockquote{ border-color: #43a047; color: #43a047;} table.grid{ border-collapse: collapse;} table.grid td, table.grid th { border: 1px solid #ddd;} .fr-fic.fr-dib{ display: block; margin: 5px auto;}.fr-fic.fr-dib.fr-fir{ text-align: right; margin: 5px 0 5px auto;}.fr-fic.fr-dib.fr-fil{ text-align: left; margin: 5px auto 5px 0;}.fr-fic.fr-dii{ float: none; margin: 5px auto;}.fr-fic.fr-dii.fr-fil{ float: left; margin: 5px auto;}.fr-fic.fr-dii.fr-fir{ float: right; margin: 5px auto;}img.fr-dib.fr-fir { margin-right: 0; text-align: right;}img.fr-dib.fr-fil { margin-left: 0; text-align: left;}img.fr-dib { margin: 5px auto; display: block; float: none;}img.fr-bordered { box-sizing: content-box; border: solid 5px #CCC;}img.fr-shadow { box-shadow: 10px 10px 5px 0px #cccccc;}img.fr-rounded { border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;}</style><style>
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
img.fr-dib.fr-fir {
margin-right: 0; text-align: right;
}
img.fr-dib.fr-fil {
margin-left: 0; text-align: left;
}
img.fr-dib {
margin: 5px auto; display: block; float: none;
}
img.fr-bordered {
box-sizing: content-box; border: solid 5px #CCC;
}
img.fr-shadow {
box-shadow: 10px 10px 5px 0px #cccccc;
}
img.fr-rounded {
border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
}
</style><style>
p {
margin: 0; font-family: "Poppins", sans-serif, "Roboto";
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
.styled-table thead tr th:first-child {
width: 28em; min-width: 28em; max-width: 28em; word-break: break-word;
}
.styled-table thead tr th:nth-child(2) {
width: 8em; min-width: 8em; max-width: 8em; word-break: break-word;
}
.styled-table thead tr th:nth-child(3) {
width: 8em; min-width: 8em; max-width: 8em; word-break: break-word;
}
.styled-table thead tr th:nth-child(4) {
width: 8em; min-width: 8em; max-width: 8em; word-break: break-word;
}
.styled-table thead tr th:nth-child(5) {
width: 8em; min-width: 8em; max-width: 8em; word-break: break-word;
}
.styled-table {
border-radius: 5px;border-collapse: collapse; margin: 25px 0; font-size: 1rem; font-family: "Poppins", sans-serif, "Roboto"; width: 100%; box-shadow: 0 0 20px rgba(0, 0, 0, 0.15);
}
.styled-table thead tr {
text-align: left;border-radius: 5px;
}
.styled-table th {
border-radius: 5px; padding: 12px 15px;
}
.styled-table td {
padding: 12px 15px;
}
.styled-table tbody tr {
border-bottom: 1px solid #dddddd;
}
.styled-table tbody tr:nth-of-type(even) {
background-color: #fafafa;
}
.styled-table tbody tr:last-of-type {
border-bottom: 2px solid $orcolor;
}
</style><p> </p><table class="styled-table grid" style="width: 100%; height: 18902px;"><colgroup><col style="width: 28.9386%;"></colgroup> <colgroup><col style="width: 12.9353%;"></colgroup> <colgroup><col style="width: 58.126%;"></colgroup><tbody><tr style="height: 51px;"><td style="text-align: left; background-color: rgb(0, 204, 248);"><strong><span style="color: rgb(255, 255, 255); font-size: 12pt;">Field</span></strong></td><td style="text-align: left; background-color: rgb(0, 204, 248);"><strong><span style="color: rgb(255, 255, 255); font-size: 12pt;">Type</span></strong></td><td style="text-align: center; background-color: rgb(0, 204, 248);"><strong><span style="color: rgb(255, 255, 255); font-size: 12pt;">Description</span></strong></td></tr><tr style="height: 159px;"><td id="app_colour_type">Application Colour</td><td>Single Select</td><td style="text-align: left;">Determines the default application colour. This will be the colour given to i.e. the navigation bar (which is displayed on the left hand side of Halo) and the configuration modules. Can be overridden per agent via their preferences, if permitted. To change this as an agent you can navigate to the picture icon in the top right hand side of the screen and then go into the preferences tab and click on the "Appearance" dropdown. The page will need to be refreshed to see the new application colour.</td></tr><tr style="height: 159px;"><td id="pagesize">Main Screen Page Size</td><td>Integer</td><td style="text-align: left;">Determines the number of records visible on a page i.e. setting to 50 would mean that 50 tickets, clients, assets, etc... will show per page. (tickets, clients, assets etc..)<br><br>Can override per agent by going to "Preferences > Usability". When this is changed from advanced settings, it will also update the field on the agent level setting, then you can reset to agent preference via agent setting, which will not change the advanced setting.</td></tr><tr style="height: 47px;"><td id="default_ticket_preview_mode">Default "List Preview Mode" for new Agents</td><td>Single Select </td><td style="text-align: left;"><span style="color: rgb(0, 0, 0); font-family: Poppins, sans-serif, Roboto; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(250, 250, 250); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;" id="isPasted">(2025 UI) Sets whether the tree menu will show or be hidden for new agents by default.</span><br></td></tr><tr style="height: 47px;"><td id="default_newtabpref">Default "Popout Display" for new Agents</td><td>Single Select</td><td style="text-align: left;">(2025 UI) Sets the behaviour for how opening in a new tab functions.</td></tr><tr style="height: 70px;"><td id="useiconsforactionbuttonsmobile">Only show icons for action buttons on mobile</td><td>Checkbox</td><td style="text-align: left;">When checked and viewing tickets in a mobile web browser, action buttons will only present the icon and not the action button name. This does not affect the Halo mobile app.</td></tr><tr style="height: 137px;"><td id="default_showmenu">Always show menu when opening a new tab</td><td>Checkbox</td><td>When checked, new tabs opened in Halo will always display the navigation menu down the left hand side. If this is not selected, the URL parameter will often end in "&showmenu=false", you can change "false" to "true" and the navigation menu will appear. An example of when the navigation menu will not show is when opening a ticket in a new tab, this setting will prevent this from happening.</td></tr><tr style="height: 231px;"><td id="navdisplaymode">Navigation menu display (Default)</td><td>Single Select</td><td>Determines how the module icons are presented on the Left hand side of the Agent application. This includes:<ul><li>Small Icons</li><li>Large Icons</li><li>Large Icons with Labels.</li></ul><p>This can be overridden at agent level: Agents > Preferences Tab > Appearance Dropdown</p><p><br></p><p>Selecting "Default" on agent level will use the option set within advanced settings, when Large icons with labels is selected the name of the area will show below the icon.</p></td></tr><tr style="height: 70px;"><td>Navigation menu colour</td><td>Single Select </td><td>Can select either the default or a custom colour that overrides the colour when you click on a module or on the tree within a module.</td></tr><tr style="height: 137px;"><td id="decimal_separator">Decimal Separator</td><td>Single Select</td><td>On figures loaded in Halo (costs, prices etc..), the selected option in this field will establish the decimal separator. can be defined to "." "," or " ' " the default is to use the server settings.<br><br>For example €1.234,56 (One thousand two hundred thirty-four euros and fifty-six cents). The thousands separator is the "." and the decimal separator is the ","</td></tr><tr style="height: 137px;"><td id="thousands_separator">Thousands Separator</td><td>Single Select</td><td>On figures loaded in Halo (costs, prices etc..), the selected option in this field will establish the thousands separator. can be defined to "." "," or " ' " the default is to use the server settings.<br><br>For example €1.234,56 (One thousand two hundred thirty-four euros and fifty-six cents). The thousands separator is the "." and the decimal separator is the ","<br></td></tr><tr style="height: 115px;"><td id="navbar_new_ticket">Display new Ticket button in navigation bar</td><td>Checkbox</td><td>When checked, a 'New Ticket' button will be available from the top navigation bar, allowing a new Ticket to be logged from any screen in the system. The default Ticket type shown on the new ticket screen (this can be changed on the ticket type field of the new ticket screen) is set via Configuration>Tickets>General Settings>*Default Ticket Type for New Tickets*</td></tr><tr style="height: 92px;"><td id="navbar_new_call">Display new Call button in navigation bar</td><td>Checkbox</td><td>When checked, this enables the use of a button at the top right of the screen which will open the New Call screen. Allowing a new call to be opened from anywhere in the system. Call scripts and Call Management settings can be configured within Configuration > Call Management.</td></tr><tr style="height: 182px;"><td id="tabnametype">Browser tab names</td><td>Single Select</td><td>Provides the choice between breadcrumb-like tab headers or the default. For example if a "My Approvals" area or advanced settings configuration is opened in a new Tab, the tab on your browser will be labelled "My Approvals" or "Configuration>Advanced Settings" instead of just saying HaloPSA or HaloITSM.<br><br><strong>Recommended to be on the breadcrumb like option, so your browsers Halo tabs will be easier to read.</strong></td></tr><tr style="height: 92px;"><td id="darkthemenotedisplay">Dark theme note display</td><td>Single Select</td><td>Allows the choice of how emails and notes are presented on the screen when the dark theme is enabled.<br>Dark theme of Halo can be enabled per agent in the Preferences Tab > Appearance.</td></tr><tr style="height: 92px;"><td id="show_kb_links">Show KB guide links against each setting (where available)</td><td>Checkbox</td><td>When enabled, a spanner icon will show next to settings across Halo. When these are clicked, it will take you to the appropriate admin guide and scroll down the page to tell you what that setting is used for. <br><br>You can toggle this on a per page basis using the "Show/Hide Guide Links" button on the top right of the page. </td></tr><tr style="height: 47px;"><td id="ticket_details_style_profile">Halo UI Style</td><td>Single Select</td><td>This can be used to select which UI style your instance follows.</td></tr><tr style="height: 70px;"><td id="default_tree_display_mode">Default "Tree menu display"</td><td>Single Select</td><td>(2025 UI) Selects whether the tree menu that shows on the left hand side, i.e. "Tickets by Team" in ticket lists, shows connected to the module bar or as a separate widget.<br></td></tr><tr style="height: 70px;"><td id="default_halo_tab_pref">Halo Tab Display</td><td>Single Select</td><td>(2025 UI) Selects whether Halo contains one tab per browser tab, or if you have multiple Halo tabs within one browser tab.</td></tr><tr style="height: 70px;"><td id="enable_widget_pop">Allow widgets throughout the app to pop-out on hover</td><td>Checkbox</td><td>(2025 UI) When enabled, widgets across your instance will pop out when hovering over them.<br></td></tr><tr style="height: 70px;"><td>Table Bulk Select Checkbox Position</td><td>Single Select </td><td>(2025 UI) Selects whether bulk action checkboxes in lists show on the left or right. If changed from the default (left) to right, the checkbox will also only show when hovering over that row.<br></td></tr><tr style="height: 70px;"><td id="tree_width">Tree menu width (px)<br></td><td>Integer</td><td>(2025 UI) Sets the pixel width of the tree menu when viewing a Ticket with it open. This only applies when Tree menu display is set to "Undocked", and the default value is 298 px.</td></tr><tr style="height: 47px;"><td id="use24hrclock">Use 24 hour clock</td><td>Checkbox</td><td>Provides a choice between a 12 or 24-hour clock, i.e. 1:00pm or 13:00. </td></tr><tr style="height: 92px;"><td id="userelativedates">Use relative dates</td><td>Checkbox</td><td>When selected, action date stamps on tickets will display dates as 'last Tuesday' (The Tuesday that just passed) if you view the ticket on the Wednesday. When not selected, dd/mm/yyyy (date formats) will always be used.</td></tr><tr style="height: 47px;"><td id="rtimezone">Time Zone</td><td>Single Select</td><td>Allows the selection of a regional Time Zone for your Halo instance.</td></tr><tr style="height: 115px;"><td id="datepickermodal">Show date-pickers in a modal window</td><td>Checkbox</td><td>Enables a calendar-like window for the population of date fields on Halo. An example would be setting a date for an appointment, the UI will be easier to navigate when selecting dates, as it pops out to the middle of the screen.<br><strong>Recommended to have this option selected.</strong></td></tr><tr style="height: 115px;"><td id="timefieldinputtype">Time field input type</td><td>Single Select</td><td>Allows the choice of how date/time fields are formatted. If the browser default is selected i.e. the Google default is used: The default is to highlight the numbers in the time field when clicked on, then inputting numbers will go from right to left. <br><strong>Recommended to use "dropdown".</strong></td></tr><tr style="height: 70px;"><td id="show_timezone_input">Show timezone input for date fields</td><td>Checkbox</td><td>Enables a dropdown alongside datetime type fields where a time zone can be selected. <strong>Supported fields: Ticket start date and time and end date and time.</strong></td></tr><tr style="height: 70px;"><td>World Clocks</td><td>Text</td><td>IANA time zone names can be entered here, and used within a ticket widget to show the time in different timezones.</td></tr><tr style="height: 70px;"><td id="hide_enddate_timezone">Hide the timezone input for end date<br></td><td>Checkbox<br></td><td>When this setting is enabled, the end date field on actions will not show the timezone input option. The timezone specified for the start date will also be applied to the end date.</td></tr><tr style="height: 47px;"><td id="default_timezone_input">Timezone input default timezone<br></td><td>Single Select</td><td>Here, choose the default time zone that will be chosen in fields that allow you to select a time zone. If "Default" is chosen then UTC will be used as the default time zone. If "User/Agent Browser" is chosen then the time zone will be taken from the browser the agent/user is using. </td></tr><tr style="height: 92px;"><td id="password_strength_level">Required Password Strength</td><td>Single Select</td><td>Provides a choice of three strengths of password requirements. These detail how many, and what type of characters are required in the password, which will determine it's security and strength. <strong>Recommended to be using Medium as the bare minimum.</strong></td></tr><tr style="height: 115px;"><td id="allownhdsupport">Allow Halo Service Desk remote support access and Single Sign On bypass option</td><td>Checkbox</td><td>When selected, staff at Halo will be able to use a 'Support Password' in order to log into your instance (for troubleshooting etc..). When unchecked, only individuals with agent accounts in your instance will be able to log in.<br><strong>Please Note: Disabling this feature will make it more difficult for Halo support to help you</strong></td></tr><tr style="height: 70px;"><td id="ssorememberme">Remember Me when using a SSO method</td><td>Checkbox</td><td>When selected & logging into Halo via SSO, a 'Remember Me' option will be available. When unselected, every login via SSO will require you to input a password.</td></tr><tr style="height: 204px;"><td id="alluse2fa">Force all Agents to use Two-Factor Authentication</td><td>Checkbox</td><td><strong>IMPORTANT:</strong> Enabling this feature without setting up 2FA will lock you out of your account, and you will have to contact Halo support. To use this feature, please first set up 2FA: <a href="https://usehalo.com/haloitsm/guides/921" target="_blank" rel="noopener noreferrer"><strong>Setting up Two Factor Authentication</strong></a><br><br>When selected, all Agents will be required to authenticate their log in via 2FA. When unselected, only those Agents with 2FA enabled (via Agent details) will require this. Make sure you have setup 2FA, this setting found below: "New Agents must set up an authenticator app upon logging in" is useful to enable when new agents use the system and do not have 2FA setup yet.</td></tr><tr style="height: 70px;"><td id="ualluse2fa">Force all Users to use Two-Factor Authentication</td><td>Checkbox</td><td>This option forces users to use Two-Factor Authentication when logging into the self-service portal.</td></tr><tr style="height: 70px;"><td id="2faemailallowed">Allow Two-Factor Authentication using email</td><td>Checkbox</td><td>This enables the use of Two-Factor Authentication via an automatic email containing a code with which to authenticate.</td></tr><tr style="height: 70px;"><td id="2fasmsallowed">Allow Two-Factor Authentication using SMS</td><td>Checkbox</td><td>This enables the use of Two-Factor Authentication via an automatic SMS message being sent to the User or Agent's phone number, containing a code with which to authenticate.</td></tr><tr style="height: 70px;"><td id="2faauthenticatorallowed">Allow Two-Factor Authentication using an authenticator app</td><td>Checkbox</td><td>This enables the use of Two-Factor Authentication via an authenticator app, such as Microsoft's or Google's "Authenticator", these are usually applications on phones.</td></tr><tr style="height: 70px;"><td id="hide2fadontshowagain">Show the "Don't ask again on this browser" option during Two-Factor Authentication</td><td>Checkbox</td><td>When checked, an option will be available during the 2FA process: "Don't ask again on this Browser". This will bypass the 2FA process on the Browser for one Month.</td></tr><tr style="height: 70px;"><td id="force_agent_2fa">New Agents must set up an authenticator app upon logging in</td><td>Checkbox</td><td>When selected, this forces agents to set up two factor authentication the next time they log into the agent application.</td></tr><tr style="height: 70px;"><td id="force_user_2fa">New Users must set up an authenticator app upon logging in</td><td>Checkbox</td><td>When selected, this forces users to set up two factor authentication the next time they log into the portal.</td></tr><tr style="height: 47px;"><td id="mobileapp_disabled">Allow Halo Mobile app access</td><td>Checkbox</td><td>When selected, your Halo instance will be accessible via the Halo IOS/Android app.</td></tr><tr><td>Use the updated new Ticket screen on the mobile app<br></td><td>Checkbox</td><td id="new_mobile_new_ticketscreen">When selected, New Tickets can be logged directly from the App, rather than being redirected to your browser. </td></tr><tr style="height: 242px;"><td id="enablepasswordfieldaudit">Enable auditing of password type fields (Recommended)</td><td>Checkbox</td><td><p>Enable password auditing to track when password fields are read.</p><p>When checked, the act of viewing Password Fields (with the eye icon) is recorded and audited in the database.</p>Halo provides the option to create 'password' type fields (Custom Fields, Site Fields, Asset Fields), where the visibility of these fields can be toggled (provided relevant permissions are granted). Checking this box will allow you to audit who views these protected fields & when they did so. <a href="https://usehalo.com/haloitsm/guides/1256" rel="noopener noreferrer" target="_blank"><strong>Guide for creating/ storing passwords</strong></a><br><strong>Recommended to have this setting selected.</strong><br><br><a href="https://usehalo.com/haloitsm/guides/2054/"><strong>Report to run for Password Audits</strong></a></td></tr><tr style="height: 115px;"><td id="allow_readall_passwords">Allow all client IDs to access all on-prem integrations which use the Halo Integrator</td><td>Checkbox</td><td>This removes any restrictions placed against clients so that they can access any On-Prem integrations that use the Halo Integrator. When this feature is disabled, all On-Prem integrations that use the Halo Integrator will have a client ID whitelist which can be configured in the setup for each integration.</td></tr><tr style="height: 70px;"><td id="allow_password_override">Allow admins to override Agent passwords</td><td>Checkbox</td><td>This allows Agents marked as Administrators to manually change another Agent's password, this doesn't allow them to view current passwords.</td></tr><tr style="height: 137px;"><td id="show_agents_forgot_password">Show the Forgot Password Link on the Agent application<br></td><td>Checkbox<br></td><td>Disabling the setting simply removes the forgot password link from the agent application login screen.<br><br><em><strong>Note: "Outgoing Email Defaults" in Configuration > Email > General Settings will need to have a Default Mailbox set.</strong></em></td></tr><tr style="height: 137px;"><td id="show_agents_forgot_password">Show the Forgot Password Link on the User application<br></td><td>Checkbox<br></td><td>Disabling the setting simply removes the forgot password link from the user application login screen.<br><br><em id="isPasted"><strong>Note: "Outgoing Email Defaults" in Configuration > Email > General Settings will need to have a Default Mailbox set.</strong></em><br></td></tr><tr style="height: 70px;"><td id="disablehalologinwithssoautoredirect">Prevent authentication with Halo credentials if single sign-on is enforced</td><td>Checkbox</td><td>This stops users / agents appending /?nosso=true to the login URL in order to bypass the SSO screen.</td></tr><tr style="height: 70px;"><td id="sso_bypass_2fa">Bypass Halo 2FA if logging in with Single Sign-On</td><td>Checkbox</td><td>This option prevents users / agents from having to perform 2FA twice, should they have 2FA enforced on their SSO application too.</td></tr><tr style="height: 92px;"><td id="allow_halo_mfa_with_sso">Allow Halo 2FA if logging in with Azure Single Sign-On<br></td><td>Checkbox</td><td>When checked, agents and users will be able to use Halo 2FA procedures when logging in with Azure single-sign on. This will store and additional cookie used to allow agents/users to skip 2FA if they have checked 'remember me' when logging in previously. </td></tr><tr style="height: 70px;"><td id="allow_agent_impersonation">Allow admins to impersonate Agents</td><td>Checkbox</td><td>Enables a button on an Agent's profile which logs admins in as the selected agent. Found in the list of actions on an agent.</td></tr><tr style="height: 70px;"><td id="allow_user_impersonation">Allow the impersonation of Users</td><td>Checkbox<br></td><td>Enables a button on an User's profile which logs admins in as the selected User. Found in the list of actions on a user.</td></tr><tr><td id="enable_portal_impersonation_selection"><p data-pasted="true">Allow portal selection when impersonating a User</p></td><td>Checkbox<br></td><td>Enabling this will show a Popup when impersonating a User allowing you ton choose which Portal to view. This setting requires Multi-Tenancy to be enabled. (This setting will only show when impersonation of Users has been permitted. )</td></tr><tr style="height: 70px;"><td id="admin_extra_read">Give admins additional privileges</td><td>Checkbox</td><td>When selected, the 'Administrator' permission on agents will override all their permissions to highest access. Giving all admins full access.</td></tr><tr style="height: 159px;"><td id="reset_security_stamps">Reset security stamps for Agents / Users each time an integration with role mappings runs, regardless of if the roles change</td><td>Checkbox</td><td>When checked and an integration runs (conventionally via halo integrator) i.e. using the agents permission level to run the integration. If for example the agent logged in as on the halo integrator is being used to sync assets to an RMM tool, but they lack the permissions for assets, therefore it will error, so you have their permissions for assets elevated. Normally you would need to regenerate the secret for the halo integrator, with this setting turned on, you will not need to regenerate a secret for the halo integrator, the security stamp will reset.</td></tr><tr style="height: 92px;"><td id="certificates">Certificates</td><td>List</td><td>This will take you to the Certificates list, where you can add and manage certificates on your system. Upload your own X.509 certificate pfx files to verify webhooks and database lookups. <strong>Do not add your SSL certificate here.</strong></td></tr><tr style="height: 359px;"><td id="update_encryption">Update encryption (n passwords / secrets to update)</td><td>Button</td><td><p>This function will attempt to update these secrets/ passwords to the current encryption certificate. Where n represents the number of secrets/passwords you will have that need updated. </p><p>Configure a X.509 certificate for encrypting password fields.</p><p><br></p><p><strong>For On-prem customers "</strong><strong>Add the property "EncryptionThumbprint" equal to your certificates thumbprint in /api/appsettings.json.</strong></p><p><strong><br></strong></p><p><strong>This certificate must be located within the LocalMachine/My store of the Server running the web application.</strong><strong>"</strong></p>This will update the mentioned Secrets and Passwords' encryption to match the most recent certificate. This cannot be done inside your current time zone's peak hours (Mon-Fri 0800-1800) as it is very resource intensive and will otherwise slow down the system.<br><br>Passwords encrypted with a different certificate or encryption method will be updated to use your encryption certificate.</td></tr><tr style="height: 92px;"><td id="next_ticket_id">(Set Next system ID) Tickets</td><td>Integer</td><td>Determines the next Ticket ID to use - For Tickets and other entities with a system ID, the below integer values will be used when creating the next entity - they will not work if there are already entities with a higher ID than the integer you input into the field.</td></tr><tr style="height: 92px;"><td id="next_invoice_id">(Set Next system ID) Invoices</td><td>Integer</td><td>Determines the next Invoice ID to use - For Invoices and other entities with a system ID, the below integer values will be used when creating the next entity - they will not work if there are already entities with a higher ID than the integer you input into the field.</td></tr><tr style="height: 92px;"><td id="next_quote_id">(Set Next system ID) Quotations</td><td>Integer</td><td>Determines the next Quotation ID to use - For Quotations and other entities with a system ID, the below integer values will be used when creating the next entity - they will not work if there are already entities with a higher ID than the integer you input into the field.</td></tr><tr style="height: 92px;"><td id="next_salesorder_id">(Set Next system ID) Sales Orders</td><td>Integer</td><td>Determines the next Sales Order ID to use - For Sales Orders and other entities with a system ID, the below integer values will be used when creating the next entity - they will not work if there are already entities with a higher ID than the integer you input into the field.</td></tr><tr style="height: 92px;"><td id="next_supplierorder_id">(Set Next system ID) Purchase Orders</td><td>Integer</td><td>Determines the next Purchase Order ID to use - For Purchase Orders and other entities with a system ID, the below integer values will be used when creating the next entity - they will not work if there are already entities with a higher ID than the integer you input into the field.</td></tr><tr style="height: 70px;"><td id="attachmentsizelimitmb">Attachment Upload Size Limit (MB)</td><td>Integer</td><td>This places a designated limit on the file-size allowed for uploading attachments to Halo. The attachment limit should be between 0 and 28 MB due to IIS restrictions.</td></tr><tr style="height: 70px;"><td id="loadimagesfromapi">Load images via the API</td><td>Checkbox</td><td>This will determine the route via which images are loaded; straight from the database, or via an API-Image Link (Available only to on-prem instances)</td></tr><tr style="height: 47px;"><td id="loadimagesfromapitype">Image Storage Location</td><td>Single Select</td><td>Dictates where images are stored. (Available only to on-prem instances)</td></tr><tr style="height: 159px;"><td id="loadattachmentsfromapitype">Attachment Storage Location<br></td><td>Single Select</td><td>The Halo attachment storage location determines where attachments are stored. If the storage location is set to 'Database,' the API will return a link to the storage location when making a GET request to a Halo attachment endpoint. If the storage location is set to 'Amazon S3,' the API will return the attachment as a Base64-encoded string when making a GET request. For more information on the API endpoint and different attachment entity types, read this article: <a href="https://usehalo.com/haloitsm/guides/2500/" target="_blank" rel="noopener noreferrer"><strong>Attachment Storage Locations and Endpoints</strong></a><br></td></tr><tr style="height: 70px;"><td>Enable Client Side Uploads<br></td><td>Checkbox</td><td>When this setting is enabled files are directly uploaded to S3 via an upload link rather than via the API. It allows you to increase the file upload limit to <strong>100mb</strong>.<br></td></tr><tr style="height: 70px;"><td id="enable_document_previewer">Allow Microsoft Office files to be viewed in the browser</td><td>Checkbox</td><td>When clicking on an attached Word, PowerPoint, or Excel file, the file will be displayed in a modal preview. Attachments can be downloaded by right-clicking them.</td></tr><tr style="height: 115px;"><td id="enablefulltextsearch">Enable Full-Text Searching</td><td>Checkbox</td><td>This returns smarter results when searching a document for phrases or sentences. In contrast to traditional searches, this will return results containing partial matches too, as opposed to exact matches. (For on-prem clients Full-Text search must be enabled in SQL Server to use this).</td></tr><tr style="height: 70px;"><td id="usefreetexttable">Full-Text search method</td><td>Single Select</td><td>This allows the choice between different formulas for Full-Text searching. The configuration of this is only available for on-prem clients.</td></tr><tr style="height: 92px;"><td id="use_new_search_method">Use new search method<br></td><td>Checkbox</td><td><strong>Recommended to use</strong><br>When checked, the "New Full-Text Search Method" option will disappear. This is an improved and more efficient search, especially when there are lots of tickets and actions to be searched.</td></tr><tr style="height: 47px;"><td id="new_search_type">New Full-Text Search Method</td><td>Single Select</td><td>Provides the option to search the full text first and then search using a contains clause.</td></tr><tr style="height: 92px;"><td id="enablefulltextsearchactions">Enable Full-Text Searching on Action notes</td><td>Checkbox</td><td>Allow for Actions that contain notes sections to be searchable using the Full-Text Searching method described in the above setting. Note that searching actions will impact search performance.</td></tr><tr style="height: 92px;"><td id="limit_action_search">Only search actions in Ticket areas and only when opting in</td><td>Checkbox</td><td>When Enable Full-Text Searching on Action notes is selected, then this dropdown will appear - it will limit the actions to search through to only the ticket areas, so excluding anywhere else actions are used. This will help to improve search performance.</td></tr><tr style="height: 70px;"><td id="searchfullticketids">Only search Ticket IDs if the search term exactly matches a Ticket ID</td><td>Checkbox</td><td>This will stop searches returning ticket results if the ticket ID happens to be included inside any other numbers in the search query, they will be returned should the ID be exactly stated.</td></tr><tr style="height: 159px;"><td id="accent_insensitive_search"><span style="color: rgb(0, 0, 0); font-family: Poppins, sans-serif, Roboto; font-size: 11pt; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; float: none; display: inline !important;">Enable accent insensitive search</span></td><td>Checkbox</td><td>When selected, accents do not have to be explicitly typed into the top left search bar of the navigation menu (not applicable to the filter search bar on columns of lists). When this checkbox is unselected accents must be included in order for names with accent letters to appear in the search.<br><br><em><strong>Note: </strong></em><strong><em>This setting can only be applied when using full-text searching</em></strong></td></tr><tr style="height: 92px;"><td id="showtreesearch">Show the Tree menu search option</td><td>Checkbox</td><td>This enables/disables the search bar at the top left when viewing tickets, assets etc... After clicking "enter" to search for your desired ticket, etc. There will be different filtering options which appear.</td></tr><tr style="height: 115px;"><td id="enablemultientitysearch">Enable searching of multiple entities at once</td><td>Checkbox</td><td>When selected, there will be a dropdown of different entities which can be searched for (Articles, Suppliers, etc...). Choose what entities are searched when using the "All" search option "<strong>L</strong><strong>ocated in the top</strong><strong> right corner of the screen</strong>". Having lots of entities selected will impact search times. It is recommended you only enable the entities that will be frequently searched for. </td></tr><tr style="height: 92px;"><td id="showquicksearch"><p>Show the quick search in the navigation bar</p></td><td>Checkbox</td><td>When checked, a permanent search bar is available at the top right of the screen, this will automatically search all entities specified on the below options. <strong>Entity filtering will not be possible in quick search with this setting enabled.</strong></td></tr><tr style="height: 249px;"><td id="lookup_search_filters">Show a multi select Field instead of checkboxes for lookup Fields in the Search Filters<br></td><td>Checkbox<br></td><td><strong>After enabling this setting log out and back into Halo for this feature to be activated.</strong><br><br>With this setting enabled, when searching in Halo via the search button in the left side navigation bar, or from the top bar if "Show the quick search in the navigation bar" is turned off within configuration > advanced settings. When you use the search functionality and i.e. filter the search by tickets via clicking the "All" option and changing the dropdown to display a search on tickets. You will then be able to use another filter (symbolised by a filter button) within to search for i.e. specific statuses. Traditionally this would display a list of checkboxes, with this new setting enabled you will see a multi select dropdown in which you can specify the statuses you want to search for.</td></tr><tr style="height: 92px;"><td id="lookup_search_filters">Choose what entities are searched when using the "All" search option<br></td><td>Checkbox(es)<br></td><td>There are a series of checkboxes below this header, this determines which entities are searched against when using the 'All' search option. if a checkbox against an entity is checked, this will be included in the search. e the more entities selected the more search times will be impacted. </td></tr><tr style="height: 90px;"><td id="enablekbfulltextsearch">Enable Knowledge Base Article Full-Text Searching</td><td>Checkbox</td><td>Adds the Full-Text searching functionality to the Knowledge Base search bar too. This will improve search times and accuracy when searching for knowledge base articles.<p>(For on-prem customers Full-Text search must be enabled in SQL Server to use this)</p><p><br></p><p>For both "Search for each word of the search string" and "Search for every word of the search string" Knowledge Base search types, this functionality will return search results which contain the whole, unbroken search phrase higher than articles which otherwise match the search phrase.</p></td></tr><tr style="height: 159px;"><td id="kbsearchmode">Knowledge Base Search Type</td><td>Single Select</td><td>Offers options on how the Knowledge Base search formula is processed. "Each" will search for the words individually, "Every" will return results where all the words are present, not necessarily in the right order. "Entire" will search for all the words in the order given on the search bar. Essentially Each will be searching for articles containing "Knowledge" or "Base", whereas Every is searching for articles containing "Knowledge" and "Base". Finally Entire is searching articles containing the entire string of words given in the search bar "Knowledge Base"<strong>.</strong><strong> </strong> </td></tr><tr style="height: 92px;"><td id="only_search_main_asset_fields">Only search main Asset fields</td><td>Checkbox</td><td>When enabled, the search bar within the Assets area will only search client/customer name, site name, inventory number, and key fields 1-3. This improves performance, especially in larger instances.</td></tr><tr style="height: 70px;"><td id="disable_async_search">Disable searching as you type<br></td><td>Checkbox</td><td>When enabled, searching will not begin until you hit enter in the search bar. Search will no longer run as you are typing, making the search more streamline. </td></tr><tr style="height: 70px;"><td id="allow_searching_ticket_reference">Enable searching on Ticket reference<br></td><td>Checkbox</td><td>When enabled, the prefix to Ticket References can be included when searching, i.e. "INC: 2783" can also be searched instead of only "2783".</td></tr><tr style="height: 68px;"><td id="hide_system_field_from_search">Limit available fields in Ticket search filter<br></td><td>Checkbox</td><td>When enabled, you will be able limit the fields that are available to be used as search filters when searching tickets. This can help streamline your search screen. Use the "Ticket filter fields" to choose which fields can be used to filter search results. </td></tr><tr style="height: 70px;"><td id="searchable_fields_list">Ticket filter fields<br></td><td>Multi Select</td><td>Only available when "Limit available fields in Ticket search filter" is enabled. Here, choose which ticket fields can be used to filter search results when searching tickets. Only system ticket fields will show here, you can control if each custom field can be used to filter the search using the <a data-fr-linked="true" href="https://usehalo.com/haloitsm/guides/1435" data-pasted="true" target="_blank" rel="noopener noreferrer">configuration of each custom field</a>. </td></tr><tr style="height: 70px;"><td id="enableonlinepresence">Enable Agent Online Status Tracking</td><td>Checkbox</td><td>This enables tracking of the last agent that was online and allows automatic changing of the agent status to idle when there is lack of activity.</td></tr><tr style="height: 92px;"><td id="idle_session_timeout_mins_agent">Agent idle timeout (minutes)<br></td><td>Integer</td><td>This input determines the amount of idle time allowed in Halo before an agent is logged out. 0 = no timeout, 5 minutes is the minimum amount. If an agent exceeds this time they will be logged out. </td></tr><tr><td id="idle_session_timeout_warning">Agent idle time warning (minutes)<br></td><td>Integer</td><td>Only available when "Agent idle timeout (minutes)" has a value. This input determines how long the agent can be idle for before they receive a warning that they will be logged out. 0 = no warning, 3 minutes is the minimum amount of time an agent can be idle for to receive a warning. When this is set agents the are idle for the number of minutes set here will receive a warning that a timeout is approaching and they are going to be logged out soon. </td></tr><tr style="height: 115px;"><td id="enable_idle_session_timeout_named_lic">Enable idle timeout for Named licenced Agents</td><td>Checkbox<br></td><td>This setting will only display if the Agent idle timeout (minutes) has a value.<br><br>The licence type: Named Licences is defined from the type of licence you have bought from Halo, with this setting enabled, the agent timeout will be activated for the Named licence type.</td></tr><tr style="height: 137px;"><td id="enable_idle_session_timeout_concurrent_lic">Enable idle timeout for Concurrent licenced Agents<br></td><td>Checkbox<br></td><td>This setting will only display if the Agent idle timeout (minutes) has a value.<br><br>The licence type: Concurrent Licences is defined from the type of licence you have bought from Halo, with this setting enabled, the agent timeout will be activated for the Concurrent licence type.<br></td></tr><tr style="height: 70px;"><td id="record_online_presence_snapshots">Record concurrent licence usage data<br></td><td>Checkbox<br></td><td>This will take a snapshot of logged in Agent count throughout the day and store it in the OnlineStatusSnapshot table.<br></td></tr><tr style="height: 70px;"><td id="limit_active_sessions">Limit Agents and Users to one active session<br></td><td>Checkbox</td><td><strong></strong>When enabled and an Agent/User logs in on another device, all other sessions will be revoked and returned to the login screen.</td></tr><tr style="height: 47px;"><td id="mainrefreshinterval">Main Screen Refresh Interval (Minutes)</td><td>Integer</td><td>Dictates how often the main screen will refresh it's data. Defaults to 2 minutes.</td></tr><tr style="height: 47px;"><td id="ticket_viewers_heartbeat_seconds">Ticket Details refresh interval (seconds)</td><td>Integer</td><td>Dictates how often the ticket details will refresh it's data. Defaults to 15 seconds.</td></tr><tr style="height: 115px;"><td id="automation_refresh_websocket">Auto-refresh Ticket Details when Automations are completed<br></td><td>Checkbox</td><td>When enabled, tickets will be refreshed automatically when automations are completed. This ensures agents are viewing the most up to date version of the ticket. This is only available when <a data-fr-linked="true" href="https://usehalo.com/haloitsm/guides/1341#enablecollisiondetection" id="isPasted" target="_blank" rel="noopener noreferrer">collision detection</a> is enabled (and, for on-prem customers, a web socket connection is configured ).<br></td></tr><tr style="height: 70px;"><td id="bulkemailbatchsize">Batch size for sending bulk emails</td><td>Integer</td><td>Dictates how many emails will be sent at a time when sending many emails to the same user at once.</td></tr><tr style="height: 92px;"><td id="integrationuserbatch">Halo Integrator User/Agent Import Batching Amount<br></td><td>Integer</td><td>Dictates how many Users/Agents are imported at one time when using the Halo integrator. This only applies to the following integrations: Azure Active Directory, Microsoft CSP, Google Workspace, Dynamics 365. </td></tr><tr style="height: 85px;"><td id="nextfaultidcalculationmethod">Next Ticket Id Calculation Method</td><td>Single Select</td><td><p>Two options: Classic and Auto-incrementing key</p><p>Auto-incrementing improves scalability and performance when creating many new Tickets per second, but a Ticket Id can no longer be specified when importing Tickets.</p></td></tr><tr style="height: 316px;"><td id="enable_new_field_data_storage_method">Enable new custom field value storage method</td><td>Checkbox</td><td><strong>This only applies to new custom fields, not pre-existing ones.<br></strong>When enabled, you can choose between two storage options when creating new custom fields - storing in a column or a row.<br><br>Storing in a row will store the field in the FieldData table, and is recommended for small numbers of ticket types.<br><br>Storing in a column will store the field in a new column in the table the field belongs to, and store the value in the same row as the entity. This is recommended for fields within a larger number of ticket types, or commonly used when listing tickets or within global searches.<br><br>If you have a larger database, storing in a row is recommended mostly as this can reduce the size of the table it is contained in, and therefore increasing performance.</td></tr><tr style="height: 115px;"><td id="new_cf_storage_method">Use the new storage method for single-select custom fields</td><td>Checkbox</td><td><strong>This only applies to new custom fields, not pre-existing ones.</strong><br>When this setting is checked, the storage of Dynamic SQL single select custom fields, will not be stored in cache when being selected, this will increase the available cache space when multiple SQL single selects are in use.</td></tr><tr style="height: 87px;"><td id="max_custom_extra_table_fields"><p id="isPasted">Maximum custom fields per custom extra table</p><br></td><td>Integer</td><td>Here you can specify the maximum width of tables that store custom field values. This setting can affect performance. The minimum value is 100, the default is 700, and the maximum is 1000.<br></td></tr><tr style="height: 137px;"><td id="agent_app_browser_suggestions">Accept browser field value suggestions in the Agent application<br></td><td>Checkbox</td><td>When checked any fields that are completed using browser suggestions will be accepted by Halo and populate the fields against the ticket successfully. When unchecked, any fields populated using browser suggestions in the agent app will not be recognised as being complete (the agent will need to complete the field manually). Enabling this setting may negatively impact application performance. </td></tr><tr style="height: 115px;"><td id="agent_visibility_type">Agent Visibility Restriction<br></td><td>Single Select</td><td>When set to 'Unrestricted', all your agents will be able to see all the other agents in the instance, they will no longer be restricted on who they can view based on their department. You will also no longer have the option to 'view tickets by agent' in ticket areas. This can be used to improve performance in instances that have large agent counts (500+). </td></tr><tr style="height: 159px;"><td id="use_arearequesttype_rules">Use criteria-based Ticket Type-Customer restrictions<br></td><td>Checkbox</td><td>When enabled, customer-ticket type restrictions will need to be <a data-fr-linked="true" href="https://usehalo.com/halopsa/guides/2055#allow_all_clients" id="isPasted" target="_blank" rel="noopener noreferrer">set at the ticket type level </a>rather than at the customer level. This can make setting restrictions easier as the customers that should or should not have access to a particular ticket type can all be set at the ticket type level. WARNING: When this is enabled any existing restrictions will not be carried over, all existing customer-ticket type restrictions will be removed and all customers will be able to access all ticket types. </td></tr><tr style="height: 65px;"><td id="control_mode">Global setting storage method</td><td>Single Select</td><td><p id="isPasted">Setting this to v2 will migrate all global settings to a new storage method, which will improve the performance of fetching global settings throughout the application and API.</p></td></tr><tr style="height: 137px;"><td id="screenlayouts">Screen Layout Profiles</td><td>Button</td><td>Takes you to the configuring of screen layout profiles. Refer to this guide for more information: <a href="https://usehalo.com/haloitsm/guides/1937" target="_blank" rel="noopener noreferrer"><strong>Ticket/ Client Areas Guide</strong></a><br><br>This can be overridden per agent by going to Agents > Preferences Tab > Screen Layouts dropdown.<br></td></tr><tr style="height: 146px;"><td id="defaultclientdetailslayout">Default Client Details screen layout</td><td>Single Select</td><td>Determines the tabs and system fields that show when viewing a client. An override can be set per agent within their preferences. Screen Layouts are constructed within the "Screen Layout Profiles" button. For more information checkout: <a href="https://usehalo.com/haloitsm/guides/1937" rel="noopener noreferrer" target="_blank"><strong>Ticket/ Client Areas Guide</strong></a></td></tr><tr style="height: 92px;"><td id="defaultuserdetailslayout">Default User Details screen layout<br></td><td>Single Select</td><td>Determines the tabs and system fields that show when viewing a user. An override can be set per agent within their preferences. Screen Layouts are constructed within the "Screen Layout Profiles" button. <br></td></tr><tr><td id="default_prospect_details_layout">Default Prospect Details screen layout<br></td><td>Single Select<br></td><td>Determines the tabs and system fields that show when viewing a prospect. An override can be set per agent within their preferences. Screen Layouts are constructed within the "Screen Layout Profiles" button. <br></td></tr><tr style="height: 92px;"><td id="default_site_details_layout">Default Site Details screen layout<br></td><td><br>Single Select</td><td>Determines the tabs and system fields that show when viewing a site. An override can be set per agent within their preferences. Screen Layouts are constructed within the "Screen Layout Profiles" button. <br></td></tr><tr><td id="default_supplier_details_layout">Default Supplier Details screen layout<br></td><td>Single Select</td><td>Determines the tabs and system fields that show when viewing a supplier. An override can be set per agent within their preferences. Screen Layouts are constructed within the "Screen Layout Profiles" button. </td></tr><tr style="height: 146px;"><td id="defaultnavscreenlayout">Default Navigation menu layout</td><td>Single Select</td><td>Sets the default layout for the Navigation Menu (icons on left-hand side). This selection is taken from the 'Screen Layout Profiles' set up already. <ul><li><a href="https://usehalo.com/haloitsm/guides/1937" rel="noopener noreferrer" target="_blank"><strong>Ticket/ Client Areas Guide</strong></a></li></ul></td></tr><tr style="height: 92px;"><td id="defaultcontractdetailslayout">Default Agreement Details screen layout<br></td><td>Single Select</td><td>Determines the tabs and system fields that show when viewing an agreement. An override can be set per agent within their preferences. Screen Layouts are constructed within the "Screen Layout Profiles" button. <br></td></tr><tr><td id="default_supplier_contract_details_layout"><br><p data-pasted="true">Default Supplier Agreement Details screen layout</p><p><br></p></td><td><br>Single Select</td><td><strong>(v2.238+) </strong>Determines the tabs and system fields that show when viewing a supplier agreement. An override can be set per agent within their preferences. Screen Layouts are constructed within the "Screen Layout Profiles" button. </td></tr><tr><td id="default_purchase_order_details_layout">Default Purchase Order Details screen layout<br></td><td>Single Select</td><td><strong>(v2.240+)</strong> Determines the tabs and system fields that show when viewing a purchase order. An override can be set per agent within their preferences tab. Screen Layouts are constructed within the "Screen Layout Profiles" button. </td></tr><tr style="height: 115px;"><td id="detailsscreendisplaytype">Details screen display mode</td><td>Single Select</td><td>Dictates the layout of the 'Details' tab on Clients, Sites, Users, and Assets. This can either be it's own tab, or located on the right hand side of the area. When pinned to the right is chosen, the details of a customer will show on a separate column on the right hand side of the main page of the customer, the first tab will be the overview.</td></tr><tr style="height: 70px;"><td id="auditdelete">Ask to enter a reason when deleting a Ticket</td><td>Checkbox</td><td>When checked, an Agent must enter a reason before a Ticket can be deleted (stored in the DB for auditing purposes).</td></tr><tr style="height: 70px;"><td id="ask_reason_client_delete">Ask to enter a reason when deleting a Customer</td><td>Checkbox</td><td>When enabled, an Agent must enter a reason before a Customer/Client can be deleted.</td></tr><tr style="height: 47px;"><td id="ask_reason_site_delete">Ask to enter a reason when deleting a Site</td><td>Checkbox</td><td>When enabled, an Agent must enter a reason before a Site can be deleted.</td></tr><tr style="height: 47px;"><td id="ask_reason_user_delete">Ask to enter a reason when deleting a User</td><td>Checkbox</td><td>When enabled, an Agent must enter a reason before a User can be deleted.</td></tr><tr style="height: 70px;"><td id="ask_reason_user_anon">Ask to enter a reason when anonymising a User</td><td>Checkbox</td><td>When enabled, an Agent must enter a reason before a User can be made anonymous.</td></tr><tr style="height: 70px;"><td id="deleteforever">Permanently delete entities from the database</td><td>Checkbox</td><td>When unselected, deleting Tickets will remove them from the UI but maintain records in the DB. When checked, Tickets are also deleted from the DB.</td></tr><tr style="height: 92px;"><td id="delete_forever_after_time">Tickets will be temporarily deleted and then permanently deleted after X number of days</td><td>Checkbox</td><td>This checkbox will show if the above is enabled. When selected, a field will show to choose the number of days that permanent deletion occurs. Before that day threshold, tickets can still be recovered.</td></tr><tr style="height: 70px;"><td id="delete_forever_after_x_days">Number of days before Tickets are permanently deleted</td><td>Integer</td><td>This field will show if the above is enabled, and will default to 30 days. The number entered here will become the number of days after deletion that permanent deletion of ticket occurs. </td></tr><tr style="height: 70px;"><td id="allow_non_admin_restore">Allow non Administrators to restore Tickets they have deleted</td><td>Checkbox</td><td>This will only show if permanent deletion is disabled. When enabled, agents with the "Can delete Tickets" permission can go to their account and click the "Restore Tickets" button at the top.</td></tr><tr style="height: 70px;"><td id="allow_non_admin_restore_time">Limit how long non Administrators have to restore Tickets they have deleted in minutes</td><td>Checkbox</td><td>When set to a number other than zero, agents will have a certain number of minutes to use the restore function mentioned above.</td></tr><tr style="height: 115px;"><td>Deleted Tickets</td><td>List</td><td>When "Permanently delete entities from the database" is unselected, This button appears, which shows a list of the Deleted Tickets. When you tick the checkbox of a ticket you will be given the options to restore the ticket(s) or permanently delete, these options can be found by hovering over the "Edit" button, which appears when you check on tickets.</td></tr><tr style="height: 70px;"><td id="keepescmsgrecord">Keep a record in the database when deleting notifications</td><td>Checkbox</td><td>Stops notification rows from being removed from the notification table in the database, instead a 'deleted' column is populated on the row.</td></tr><tr style="height: 70px;"><td id="enableconfigchangetracking">Enable config change tracking</td><td>Checkbox</td><td>When enabled, this will begin the logging of config changes, which will aid disaster recovery and fault detection. <strong>Recommended to turn this setting on.</strong></td></tr><tr style="height: 92px;"><td id="enable_mailbox_config_change_tracking">Enable config change tracking for mailboxes<br></td><td>Checkbox</td><td>When enabled, this will begin the logging of config changes to mailboxes. This setting is required to be enabled if you would like to create mailbox credentials for non-production instances. <strong>Recommended to turn this setting on.</strong></td></tr><tr style="height: 159px;"><td id="disable_tracked_editing">Disable editing of config tracked entities in production<br></td><td>Checkbox</td><td>When enabled, any entities that are config tracked will not be able to be edited in your production instance. This includes any settings/modules that are found under the 'configuration' module and any other entities you have in your instance that are config racked (such as assets). This should be enabled when you would like changes to only be made in a UAT/Dev instance and then have these changes pushed to your production, rather than allowing configuration changes to be made in your live environment. </td></tr><tr style="height: 92px;"><td id="enable_config_sprints">Use sprints for config tracking</td><td>Checkbox</td><td>When enabled, a time period for a sprint can be selected. This allows syncing between instances to be done in sprints, although this must all be done in order (A later sprint cannot be merged before a older sprint).</td></tr><tr style="height: 47px;"><td id="config_sprint_startdate">Sprints start date</td><td>Date</td><td>Specifies a start date for a sprint. This must be in the past.</td></tr><tr style="height: 47px;"><td id="config_sprint_period">Sprints period</td><td>Single Select</td><td>Specifies the time period for each sprint.</td></tr><tr style="height: 47px;"><td id="config_sprint_duration">Sprint duration</td><td>Integer </td><td>Specifies how many of the time period are a part of each sprint. </td></tr><tr style="height: 182px;"><td id="enable_services_config_change_tracking">Enable config change tracking for services<br></td><td>Checkbox</td><td>When enabled, assets that are marked as a 'Service' or 'Business Application' will have the changes made to them tracked through configuration change tracking. This can make syncing between instances easier when assets and services are being managed as one entity (Configuration Items) as changes to the service assets can be synced between instances. Being able to mark an asset as a 'Service' or 'Business Application' is dependent on 'Allow automatic linking of Assets and Service Catalogue' being enabled (Configuration > Asset Management > General Settings). </td></tr><tr style="height: 70px;"><td id="enable_reporting_config_change_tracking">Enable config change tracking for Reports and Dashboard</td><td>Checkbox</td><td>When enabled and Reports/Dashboards are created/edited/deleted, this will show in config change tracking. This allows these to be synced between instances/</td></tr><tr style="height: 259px;"><td id="dont_check_commit_diffs">Don't check diffs when getting changes to sync<br></td><td>Checkbox</td><td>Controls how changes are synced between instances. When enabled, when changes are synced between instances the differences between instances will not be checked to see where differences lie and only push differences. Instead, all changes since the last sync date will be pushed. This results in a faster loading of the instances area but potentially less accurate syncing of changes. <br><br><p>Only enable this setting if you are using <a data-fr-linked="true" href="https://usehalo.com/haloitsm/guides/1888" id="isPasted" target="_blank" rel="noopener noreferrer">instance pipelines</a>, in which changes are always made in Dev/UAT and pushed in a single direction. Once enabled do not perform manual syncs of changes (i.e. cherry-picking changes to sync). Also keep in mind when this is enabled the number of of commits behind/ahead for an instance may not be accurate but the instances area will load faster. </p></td></tr><tr style="height: 294px;"><td id="configchanges">View config changes</td><td>Button</td><td>Sends you to a page that shows all the different auditable configuration changes made on Halo, such as settings being turned on/ off. The entities which have config tracking on them, such as "Ticket Types" under Configuration>Tickets>Ticket Types will be marked with a blue icon Top right hand side of the page. When the icon is clicked on, it will take you to the list of config changes. These tracked changes can be rolled back to if a mistake is made. So if you made a mistake when configuring Halo, you can roll back everything you done to just before that mistake was made.<strong> </strong>A change that would be tracked for example is a checkbox being turned on. So this setting is very useful to see what checkbox or settings you have configured and whether or not you want to roll them all back. <strong>The roll back will undo everything done after and including the config change you rollback to</strong>. <br><a href="https://usehalo.com/haloitsm/guides/1888" rel="noopener noreferrer" target="_blank"><strong>Config Change Tracking Guide</strong></a><br><strong>Note: Deletes cannot be rolled back</strong></td></tr><tr style="height: 159px;"><td id="only_pull_config_changes">Do not allow config changes from other instances to be pushed to this instance<br></td><td>Checkbox</td><td>When enabled, configuration changes will not be able to be pushed into this instance from another instance. Changes will only be pulled into this instance from the current instance. This is used if admins are not the same between instances. Preventing admins in once instance pushing changes into another instance that they are not an admin of. This will impact how you <a data-fr-linked="true" href="https://usehalo.com/haloitsm/guides/1888" id="isPasted" target="_blank" rel="noopener noreferrer">sync changes between instances</a>, as you will no longer be able to push changes, only pull them in. <br></td></tr><tr><td id="search_control_settings">Search for Settings in Configuration<br></td><td>Checkbox</td><td>When enabled, you will be able to search for configurations settings using the search bar in the configuration module. Checkout <a target="_blank" rel="noopener noreferrer" data-fr-linked="true" href="https://usehalo.com/haloitsm/guides/1699" data-pasted="true">Searching Entities</a> for more information. </td></tr><tr style="height: 87px;"><td id="config_view_default"><p data-pasted="true">Default configuration view</p></td><td>Single Select </td><td>This dropdown allows you to decide if all, inactive or active features are shown in configuration. This can be overridden using the Eye icon at the top right in "All Features".</td></tr><tr><td id="use_thirdparty_id_config_matching"><br>Use third-party IDs for linking Agents, Users, Roles, Teams, and CABs to change tracked entities</td><td>Checkbox</td><td><strong></strong>Used when you have multiple linked instances (Dev/UAT/Prod) and are syncing changes between instances. When enabled, entities will be linked using their third party ID rather than their Halo ID. This means when changes made to an entity (such as an asset or user) are synced to another instance the entity that is updated will be the entity with a matching third party ID. When in use you must ensure the "third_party_relational_id" field against each entity contains the third party ID, this field is used to match matches/links. Data an be imported into this field using a native Halo integration, when setting up the integration ensure you have mapped a value to "third_party_relational_id". Currently, this only applies to the listed entities. </td></tr><tr style="height: 92px;"><td id="useeventservice">Use Event Service</td><td>Checkbox</td><td>Enables the features coming with the new Event Service updates. Other event processing services have been deprecated so this will be on automatically and not be able to been disabled. </td></tr><tr style="height: 92px;"><td id="useoutgoingservice">Use Outgoing Service </td><td>Checkbox</td><td>Enables the new outgoing mail service which is significantly faster than the previous. Other email processing services (NHServer) have been deprecated so this will be on automatically and not be able to be disabled. </td></tr><tr style="height: 115px;"><td id="useincomingservice">Use Incoming Service </td><td>Checkbox</td><td>Enables the new incoming mail service which is significantly faster than the previous. Enables the new incoming mail service which is significantly faster than the previous. Other email processing services (NHServer) have been deprecated so this will be on automatically and not be able to be disabled. </td></tr><tr style="height: 70px;"><td id="useschedulingservice">Use Scheduling Service</td><td>Single Select</td><td>Dictates whether the NHServer can schedule events, such as sending emails. NHServer has been deprecated so this will not be able to be disabled. </td></tr><tr style="height: 115px;"><td id="backendservicemonitoring">Backend Service Monitoring</td><td>Button</td><td>Requires the scheduling service to be on for this button to show in the list. Opens the monitoring service where the multiple different email logs can be viewed to i.e. see if there is anything not sending or being received in emails. This is also used to monitor the task scheduler, the halo integrator logs, scheduled emails and automations.</td></tr><tr style="height: 47px;"><td id="">Unsent Emails</td><td>List</td><td>Shows a list of Emails that are queued for or have failed sending.</td></tr><tr style="height: 70px;"><td id="">Clear Unsent Actions</td><td>Button</td><td>Requires the scheduling service to be off for this button to show in the list. Clears and ignores any actions that have not been processed yet.</td></tr><tr style="height: 92px;"><td id="">Clear Unsent Email Store</td><td>Button</td><td>Requires the scheduling service to be off for this button to show in the list. Clears and ignores any emails in EmailStore that have not been processed yet. (EmailStore contains object-related emails, i.e. non-ticket related.)</td></tr><tr style="height: 70px;"><td id="">Clear Unsent Notifications</td><td>Button</td><td>Requires the scheduling service to be off for this button to show in the list. Clears and ignores any notifications that have not been processed yet.</td></tr><tr style="height: 92px;"><td id="">Clear Stuck Actions</td><td>Button</td><td>Requires the scheduling service to be off for this button to show in the list. Clears any unsent emails from the system that have originated from an Action, and have already failed to send at least once.</td></tr><tr style="height: 92px;"><td id="">Clear Stuck EmailStore</td><td>Button</td><td>Requires the scheduling service to be off for this button to show in the list. Clears any unsent emails from the EmailStore that have already failed to send at least once. (EmailStore contains object-related emails, i.e. non-ticket related.)</td></tr><tr style="height: 70px;"><td id="cleanhtmlpasting">Clean up formatting when pasting from HTML</td><td>Checkbox</td><td>This will intelligently alter the formatting of the text pasted from HTML into something more readable.</td></tr><tr style="height: 182px;"><td id="agentlinkedusermanagementenabled">Allow automatic linked User management for Agents</td><td>Checkbox</td><td>If enabled, a user profile will be created automatically for each agent, this user profile will be linked to the agent profile. User creation takes place once the agent is given membership to a department. The user will be created under the customer that is linked to the organisation the agent is under (this is determined by the agent's department membership). If the agent is removed from the department, the created user is made inactive. If disabled, users will not be created automatically for each agent, instead you will have the option against each user profile to choose who the linked agent is. </td></tr><tr style="height: 47px;"><td id="trackticketviews">Record Ticket views</td><td>Checkbox</td><td>Enables the logging of ticket viewing stats, in the FaultsViewLog table.</td></tr><tr style="height: 115px;"><td id="">Use '[ID ]' as an additional subject tag check for Ticket matching</td><td>Checkbox</td><td>This option will use the default ticket matching tag alongside whatever else is specified in the Email configuration. Referencing the Email Start and End tags configured in Configuration > Email > General Settings. Then the optional checkbox for matching tickets by using tag on email subject can also be set (located below the email tag text boxes).</td></tr><tr style="height: 92px;"><td id="">Send default Ticket PDF when a Ticket is closed and contains a Signature attachment (Signature.JPG)</td><td>Checkbox</td><td>(Legacy) This can be used to avoid the issue where signatures were created using the old QR2 designer, and would mess up the emails.</td></tr><tr style="height: 70px;"><td id="htmltemplateeditortype">HTML Template Editor Type</td><td>Single Select</td><td>Enables the 'Toggle HTML Editor' option when altering HTML in PDF templates. (Configuration>Reporting>PDF Templates)</td></tr><tr style="height: 70px;"><td id="default_editor_font_family">Default Editor Font</td><td>Single Select</td><td>The font here will be set as the default for text throughout Halo, such as "Note" fields on ticket actions or within an article.</td></tr><tr><td><p data-pasted="true" id="default_rich_editor_style">Default Rich Text Editor Toolbar Style</p></td><td>Single Select<br></td><td>This drop-down allows you to choose between a static and Pop-out font style option of the Rich Text Editor Toolbar.</td></tr><tr><td id="use_custom_help_menu">Enable custom help menu<br></td><td>Checkbox</td><td><strong></strong>Enabling this setting will show a table where you can add and adjust the options shown in the Help menu.</td></tr><tr style="height: 92px;"><td id="enableagentcheckins">Enable Agent check-ins</td><td>Checkbox</td><td>When checked, Produces a "How am I feeling" section on the home screen for Agents which can then be reported on. In the reporting module, head to the online repository and search for "Agent Check In"</td></tr><tr style="height: 92px;"><td id="lookup78edit">Customise responses</td><td>Button</td><td>Found on the right hand side of the page, as a button. The text on the different responses agents can choose from on the check-in can be customised using this button, the colour of the response can also be customised.</td></tr><tr style="height: 47px;"><td id="enableagentreactions">Allow Agents to react to actions</td><td>Checkbox</td><td>This allows a range of emoji reactions to be used on individual actions.</td></tr><tr style="height: 70px;"><td id="trophy_agents_list"><p>Agents with the Halo Trophy</p></td><td>Multi Select</td><td>Here, you can select agents that have the coveted Halo Trophy. Agents selected here will have a fabulous trophy icon displayed against their name in lists and their profile icon. </td></tr><tr style="height: 115px;"><td id="enable_agent_ticket_merge_permission">Enable a Agent/Role Permission to restrict Agents from merging Tickets<br></td><td>Checkbox</td><td>When checked, an additional agent permission will become available to allow you to restrict which agents can merge tickets. When this is enabled all agents/roles will be given this permission as 'yes' by default so ensure you amend this against each agent/role you would not like to be able to merge tickets. </td></tr><tr style="height: 105px;"><td id="enable_agent_status_permission">Enable a Agent/Role Permission to restrict the Agent from manually changing their Status<br></td><td>Checkbox</td><td><p id="isPasted">When checked, an additional agent permission will become available to allow you to restrict which agents can change their agent status manually. When this is enabled all agents/roles will be given this permission as 'No' by default so ensure you amend this against each agent/role you would ]like to be able to change their own status.</p></td></tr><tr style="height: 70px;"><td id="enable_agent_status_change_logging">Enable logging of Agent Status Changes</td><td>Checkbox</td><td>When enabled, changes to agent's statuses will be recorded in the "AgentStatusChangeLog" table, which can then be reported on. It will show what the change was, who made it and when.</td></tr><tr style="height: 159px;"><td id="enable_agent_cost_table">Enable Agent Cost History Tracking<br></td><td>Checkbox</td><td>When enabled, the 'Cost per Hour' field on Agent profiles will be replaced with an 'Agent Cost Tracking table'. This means multiple historical Agent cost records can be stored for each Agent, allowing you to accurately report on historical, as well as current costs. You will also be able to choose the currency Agent cost is recorded in for each Agent, rather than the cost being recorded in the default currency. For more information check out <a data-fr-linked="true" href="https://usehalo.com/halopsa/guides/2608" id="isPasted" target="_blank" rel="noopener noreferrer">Agent Cost Tracking and Profitability Reporting</a>.</td></tr><tr style="height: 70px;"><td id="team_leader_can_edit_agent_prefs">Allow Team leaders to edit Agent preferences<br></td><td>Checkbox</td><td>When enabled, Agents marked as a "Team Leader" in a Team will be able to edit Details and Preferences of Agents in that Team.</td></tr><tr style="height: 47px;"><td id="enable_agent_display_names">Enable Agent Display Names<br></td><td>Checkbox</td><td>When enabled, agents will have an additional preference option "Display Name". This can be used to choose another name to show to users in the portal rather than the agent's actual name being used. Useful when you would not like to users to see the agents actual name. The name chosen here will replace all occurrences the the agent's name in the portal, including places in which their name is pulled through with a dollar variable. </td></tr><tr><td id="access_control_allow_department">Allow access control to be based on department</td><td>Checkbox<br></td><td>When enabled administrators can assign access control for agent departments. </td></tr><tr style="height: 70px;"><td id="enablehalonews">Enable Halo news and seasonal theme notifications</td><td>Checkbox</td><td>This allows news items from Halo to be displayed in the customer's Halo instance. These are published via Halo themselves.</td></tr><tr style="height: 47px;"><td id="track_category_id">Track Ticket category by ID and name</td><td>Checkbox</td><td>This must be selected if you want to allow ticket categories to be translated to other languages.</td></tr><tr style="height: 70px;"><td id="warn_customtable_delete">Prompt for confirmation when deleting a custom table row</td><td>Checkbox</td><td>When Checked, shows a prompt for confirmation when removing a custom table row.</td></tr><tr style="height: 92px;"><td id="assetdateformat">Format to use for Asset/Site date fields</td><td>Integer</td><td>This value corresponds to date format used for different regions. i.e. 103 = dd/mm/yyyy, 101 = mm/dd/yyyy the codes are used to change how the sql interprets the datetime fields for assets and sites.</td></tr><tr style="height: 180px;"><td id="reservedboolfield1">Disable Entity Framework for saving incoming emails via the incoming service</td><td>Checkbox</td><td>This setting changes how downloaded email data is saved in the incoming service. Adds additional checks to make sure downloaded message data has been saved correctly.<br><br>This is a niche setting which may be required to use if the email rules you are using have multiple field mappings with complicated and inconsistent values to find in between the tags, there are various other factors which can affect email processing when there are multiple complicated field mappings.</td></tr><tr><td id="log_reportevent_data">Audit when reports are run<br></td><td>Checkbox</td><td>When enabled reports will be audited. Each time a report runs an entry will be added to the ReportEvent table containing information about the report at the time it was run. This is useful for auditing but having this enabled will increase bloat in your database so it is advised to have this disabled if not needed. </td></tr><tr style="height: 70px;"><td id="max_xls_rows">Maximum number of XLS rows that can be imported at once</td><td>Integer</td><td>When set to a value other than 0, only that number of rows can be imported via XLS anywhere within the system. if set to 0, this is disabled.</td></tr><tr style="height: 115px;"><td id="use_v2_nextactivitydate">Use V2 Next Activity Date</td><td>Checkbox</td><td>Improves performance when listing tickets by "Next Activity Date".<br><br>Once enabled, a background task will queue to update the data. This could take up to an hour to complete.</td></tr><tr style="height: 70px;"><td id="include_automation_sla_action">Include Automation actions for Last private/public action<br></td><td>Checkbox</td><td>When enabled, any Variable that begins with "SLAHOLDACTION" will include Automated Actions as the last Action.</td></tr><tr style="height: 159px;"><td id="lookupcodes">Lookup Codes</td><td>Button</td><td>When clicked into, it takes you to a list of lookup codes. For an explanation of the entity for quote statuses and how to create them, checkout this guide: <a href="https://usehalo.com/haloitsm/guides/1989" rel="noopener noreferrer" target="_blank">Quotation Statuses</a>. Topic 2 of this guide: <a href="https://usehalo.com/haloitsm/guides/1901" rel="noopener noreferrer" target="_blank">Holiday Management</a> explains how holiday types are made and that they are stored as a lookup code. Most of the entities in the Lookup codes appear as a configurable option somewhere else in Halo, such as the "Asset Matching Value Exclusions" button found at the bottom of the page of Configuration><a href="https://usehalo.com/haloitsm/guides/1340" rel="noopener noreferrer" target="_blank">Asset Management>General Settings</a>. </td></tr><tr style="height: 92px;"><td id="userwayaccount_agent">UserWay Data Account</td><td>Text</td><td>Adding your UserWay Data Account here will allow the UserWay widget to be displayed on the Agent Application. This Data Account can be found in the embed code provided by UserWay on your account.</td></tr><tr style="height: 70px;"><td id="userguiding_id">UserGuiding Container ID</td><td>Text</td><td>Adding your UserGuiding Container ID here will allow the UserGuiding overlay on your instance. You will find this ID in the Containers tab in your UserGuiding settings.</td></tr><tr style="height: 47px;"><td>Show custom refresh rate setting on widgets<br></td><td>Checkbox<br></td><td>When enabled the option to change the refresh rate will show against a widget when it is edited. </td></tr><tr><td id="show_harvest_widget_ticket_tab">Show Harvest Timer Tab on Tickets<br></td><td>Checkbox</td><td>When enabled you will see a Harvest Timer tab against your Tickets. On this tab you can connect to your Harvest account to view your Harvest Task/Project timer.<br></td></tr><tr><td id="variable_suggestions">Allow Variable Suggestions<br></td><td>Single Select<br></td><td><strong data-pasted="true"></strong>Here you can select to view suggested variables from a list or text search in certain configuration areas. The variable text search option will show a list of suggested variables when the dollar symbol ($) is typed. The Insert variable from list option behaves similar to Canned Text, showing an Ohm symbol (Ω) in your text editor which displays a list of suggested variables when clicked.</td></tr><tr><td id="validate_action_outcome">Validate outcome when actions are posted without outcome IDs</td><td>Checkbox</td><td><strong>(v2.238+)</strong> When enabled if posting the 'outcome' parameter to the actions endpoint to create an action, without a the 'outcome_id' parameter, action restrictions will be checked and validation will determine if this action is available for the workflow/agent. We recommend enabling this for increased security. </td></tr></tbody></table><p><br></p>
