<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><p><strong>In this guide we will cover:</strong></p><p><strong>- How to have a second end user portal set up</strong></p><p><strong>- Customise the Branding of each portal</strong></p><p><strong>- Customise Portal CSS</strong></p><p><strong>- Customise Portal Language </strong></p><p><strong>- Setting Portal Access</strong></p><p><strong><span style="font-size: 11pt;">- <strong id="isPasted">Distributing portal URLs using $-Variables</strong></span></strong></p><p><strong>- Restricting Portal Button Access</strong></p><p><strong>- Restricting Portal FAQ list access</strong></p><p><strong>- Restricting Service access based on Portal </strong></p><p data-pasted="true"><strong>- Enforcing Ticket Type restrictions based on Portal</strong></p><p data-pasted="true"><strong>- Portal Selection when impersonating a User</strong></p><p><br></p><p><br></p><p>In your Halo, you will have an end user portal setup out-of-the-box, providing your users with a platform to access/manage their data. This portal can be customised to fit your branding, however, you may require more than one portal for your users to access. This may be as you have multiple organisations using your Halo (Multi-Tenancy), each with their own branding. Or perhaps your customer(s) require their portal domain to be in line with their company name. There are various reasons you may benefit from having more than one end user portal in your Halo instance.</p><p><br></p><p><strong><em>Note: The functionality of portals is configured globally, this means configuration settings cannot differ between your original portal and any additional portals you have set up. Additional portals allow a difference in branding/appearance rather than functionality, but functionality differences can be set per customer/organisation/user. </em></strong></p><p><br></p><p><strong><span style="font-size: 14pt;">How to have a second end user portal set up</span></strong></p><p>If you would like an additional portal set up please contact our support team with the desired URL for the portal, then we can begin getting the portal deployed for you.</p><p><br></p><p>If your users use single-sign-on to log in to your current portal, they will also be able to use this to sign in to the second portal. You do not need to carry out any additional configuration for this, we will set this up on deployment. </p><p><br></p><p><strong><span style="font-size: 14pt;">Customise the Branding of each portal</span></strong></p><p>The default portal branding, such as portal title, theme, colour and logo can be set for each portal in serval ways is set under Configuration > Self Service Portal. However, the branding can be different for each of your portals.</p><p><br></p><p><strong><span style="font-size: 12pt;">Branding per organisation (only applicable if using Multi-Tenancy)</span></strong></p><p>If you have organisation specific portals you can set the branding of the portal to be in line with the associated organisation. </p><p><br></p><p>Head to Configuration > Organisation > Configure Organisations > select an organisation, under the Details tab are some settings that determine branding used for a user portal (see <strong>Fig 1</strong>).</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjM3MjczZDMzLTA2MDctNGIyNC1iZjNiLWQxODI4NGUxMGZlZCJ9.X2HnGZZouVL5ILSZ4clbbwebuaTbcfuo6OL3FLrivgU" class="fr-fic fr-fil fr-dib" width="989" style="width: 991px; height: 588.066px;" height="588"></p><p><strong><span style="font-size: 10pt;">Fig 1. Set organisation branding</span></strong></p><p><br></p><p>Set these to determine the branding used for this organisation. Once set head to Configuration > Integrations > Halo API > View Applications > select the application for your 2nd portal > Edit, now you can set this portal to use the branding of this organisation.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjNlN2IwNDNhLWI0ZTEtNDA0YS1iZmQxLTY0NDVhMWJiZDg4YiJ9.ltIcw48kEcbaH27TdOrIrGGm4IP1pVZ1vrER9JwT4pI" class="fr-fic fr-fil fr-dib" width="917" style="width: 919px; height: 708.396px;" height="708"></p><p><span style="font-size: 10pt;"><strong>Fig 2. Set which organisation's branding is used for the portal</strong></span></p><p><br></p><p>Now whenever a user logs into this portal they will see the branding associated with the selected organisation, regardless of any organisation restrictions against the customer. </p><p><br></p><p><strong><span style="font-size: 12pt;">Branding per customer </span></strong></p><p>Head to Customers > select a customer profile > Settings > expand Override Organisation Details, here you can set the branding for this customer. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImFlYTAxNmVhLWI0NWEtNDM0OC1iZmY1LWIyZGM3ZTE5MWIzYyJ9.ehs0O9mNfiqLtvVlPOXAec0RCt5lscyOwoM8DD6Ru84" class="fr-fic fr-fil fr-dib" width="990" style="width: 992px; height: 614.465px;" height="614"></p><p><span style="font-size: 10pt;"><strong>Fig 3. Set branding for customer</strong></span></p><p><br></p><p>When branding against a customer is set this will override the branding on whatever portal a user under this customer logs in to, overriding the branding set against the portal itself. Therefore, if using customer specific portals you will need to set branding against each customer, if a customer has no branding against them the default branding set in Configuration > Self Service Portal will be used. </p><p><br></p><p>The portal web announcement and chat profile can also be set against the customer too. This is set under the Self Service Portal dropdown against the customer profile. When set these will determine the web announcement and chat profile that appear on the portal(s) for users under this customer, overriding the web announcement/chat profile set at the global and organisation level. </p><p><br></p><p>If an additional portal has been created that is intended to be used for one customer in particular you can set the branding the portal to use this customer's branding. Head to Configuration > Integrations > Halo API > View Applications > select the application for your 2nd portal, here setting 'Single Customer Access' will determine the branding used for the portal, the branding of the selected customer will be used. This will not restrict users outside of this customer being able to use this portal, but if they do they will see the branding of this customer. </p><p><br></p><p><strong><em>Note: 'Single Customer Access' is only applicable to end user portals, so will only appear when 'Allow End-User Logins' (against the application) is enabled. If setting up an agent only portal, you will need to set the branding using the organisation rather than the customer.</em></strong></p><p><br></p><p><strong><span style="font-size: 14pt;">Customise Portal CSS</span></strong></p><p>If you are using organisation specific portals you can configure custom CSS to be used per portal. </p><p><br></p><p>To do this you will first need to head to Configuration > Self Service Portal and enable 'Allow CSS customisation for multiple portals', once enabled the portal CSS will be stored as a message group email template. Therefore, a message group will need to be set up per organisation/per portal to determine what CSS is used for which portal. </p><p><br></p><p>To do this first create a message group for each for your organisations and assign them to their associated organisation. Information on how to do this can be found in the Message Group Overrides section of our <a data-fr-linked="true" href="https://usehalo.com/haloitsm/guides/2330/" id="isPasted" target="_blank" rel="noopener noreferrer"><strong>Multi-Tenancy guide</strong></a>. Now head back to Configuration > Self Service Portal and select the 'Custom CSS' button to edit the CSS. On this page you will see a template for each of your portals/organisations, each template will have an associated message group ID. You can select a template and edit it to change the CSS. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjMxZTZjYzg4LTc5OWItNGNkYi05MTdjLWIwMWZkNjQ3MDZmZiJ9.JiTMRQmchKSJ_C7lA5EOPUhAFYL05B4F7vrUISMPyTk" class="fr-fic fr-fil fr-dib" width="979" style="width: 981px; height: 274.713px;" height="275"></p><p><strong><span style="font-size: 10pt;">Fig 4. Message group ID against CSS template</span></strong></p><p><br></p><p>The message group ID against the template can be used to identify which portal this CSS will apply to. For example, the template ID=1707 is associated with message group 1. If I head to Configuration > Email > Message Groups > select a message group I can see what ID this message group has, my message group with ID 1 is called 'Halo International'.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjNmNmNiMjk0LTA2NjItNDc5ZS1iMDYyLTkxNjJlYzRlYjk2MSJ9.u8gyGi3TrBPspj00J0SFd1cyKcPuSv_Ifxrftgr8G6o" class="fr-fic fr-fil fr-dib" width="536" style="width: 538px; height: 453.542px;" height="454"></p><p><strong><span style="font-size: 10pt;">Fig 5. Message group ID</span></strong></p><p><br></p><p>I have applied this message group to my organisation 'International Halo'. Therefore, this CSS will be applied to the portal that is set to use the branding of the organisation 'International Halo'. </p><p><br></p><p><strong><span style="font-size: 14pt;">Customise Portal Language </span></strong></p><p>The language that the portal uses can be set on various levels. </p><p><br></p><p>If using multiple portals the language can be set against each portal itself. Head to Configuration > Integrations > Halo API > View Applications > select the application for your 2nd portal, here you can set the default language the portal uses.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijc5YzhlMGFhLWE4NjctNDE1Zi04YTkzLWUyNmIwNTE5NGIxZiJ9.yZLfYzdOagsglhiJilvUqira8oDeKbbhFvuIMnKNWEc" class="fr-fic fr-fil fr-dib" width="989" style="width: 991px; height: 679.354px;" height="679"></p><p><strong><span style="font-size: 10pt;">Fig 6. Default language for portal </span></strong></p><p><br></p><p>The language of portals can also be set against each customer site, to set this head to the site profile > Settings tab > advanced, use the setting 'Portal Language'. When set this will override the default language set against the portal, this will be the language all portals appears in for any users under this site. Users will still be able to override this and choose their preferred language within the portal. </p><p><br></p><p><strong><span style="font-size: 14pt;">Setting Portal Access</span></strong></p><p><strong><span style="font-size: 12pt;">Agents vs Users</span></strong></p><p>An additional portal can be configured to be accessed by end user, or by agent logins, not both. Only the default portal can be accessed by either log in. To determine if the additional portal allows user or agent logins head to h<span style="color: rgb(0, 0, 0); font-family: sans-serif; 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(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;" id="isPasted">ead to Configuration > Integrations > Halo API > View Applications > select the application for your 2nd portal, and enable the appropriate checkbox, highlighted in <strong>Fig 5</strong>. </span></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImM1YTU5Yzg0LTU0NDctNDE1NS05MWQ3LTM0ZTFiZTBkNDllNSJ9.1QuO4yTYZC6B0kJXcqBiSE-1-IPY2g82mG_J2_UZP5k" class="fr-fic fr-fil fr-dib" width="365" height="293"></p><p><strong><span style="font-size: 10pt;">Fig 7. Allow agent/user logins</span></strong></p><p><br></p><p><span style="font-size: 12pt;"><strong>Anonymous access</strong></span></p><p>You can set against each portal whether users are required to log in in order to access it. However, in order to allow anonymous access to an additional portal you will need to allow anonymous access to the default portal too. </p><p><br></p><p>To do this head to Configuration > Self Service Portal, disable 'Require Users to login to access the portal'. Now head to<span style="color: rgb(0, 0, 0); font-family: sans-serif; 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(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;" id="isPasted"> Configuration > Integrations > Halo API > View Applications > select the application for your 2nd portal, now you will be able to toggle on/off 'Allow Anonymous Access'. If users are required to log in to the default portal they will also be required to log into any additional portals. </span></p><p><br></p><p>Any user in your instance can log into any of your portals, provided they have the URL. Therefore, if you have customer specific portals you will want to only give out the portal URL to the users of the customer this portal is for. This can be done using $-variables in your email templates.</p><p><br></p><p><strong><span style="font-size: 14pt;">Distributing portal URLs using $-Variables</span></strong></p><p>We have a few variables that can be used in an email template to provide the user a link to their ticket or to the portal:</p><p><br></p><p><strong>$PORTALURL</strong> - Will provide the user a link to the portal (can also be used in live chat)</p><p><strong>$HELPDESKURL </strong>- Will provide the user a link to the portal</p><p><strong>$LINKTOREQUESTUSER</strong> - Will provide the user a link to the current ticket in the portal</p><p><br></p><p>Using $-variables to provide a link to the ticket/portal is especially useful when you are using multiple portals as it ensures the user is always directed to the correct portal for that ticket. </p><p><br></p><p>If you have additional portals you will need to set which portal will be linked, see below on how to do this.</p><p><br></p><p><strong><span style="font-size: 12pt;">For organisation specific portals:</span></strong></p><p><strong><em>Note: This is only applicable if using Multi-Tenancy.</em></strong></p><p><br></p><p>Under Configuration > Organisations > Configure Organisation > select an organisation, enter the URL of the portal associated with this organisation in the 'Portal URL' field. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjFlOWJkYmNlLWQ4ZmYtNDhlOC05YjliLTZkNTNiZWJiOWU0NCJ9.MluaXdp9KlDAhyDwvda3yBcJMxg3Of3TKpcKQ9RLyOQ" class="fr-fic fr-fil fr-dib" width="595" style="width: 597px; height: 369.96px;" height="370"></p><p><strong><span style="font-size: 10pt;">Fig 8. Setting portal URL field against organisation</span></strong></p><p><br></p><p>Once populated this field will be used to populate portal $-variables. This means if one of these variables is used the user will be sent a link to the portal of the organisation that is working on that ticket. (If the organisation that is working on the ticket does not have this field populated, the user will be linked to the default portal). </p><p><br></p><p><strong><span style="font-size: 12pt;">For customer specific portals:</span></strong></p><p>If using customer specific portals, the portal URL associated with that customer will need to be set against each customer profile to determine what URL the variable links to when sent to this customer. </p><p><br></p><p>To do this head to the customer profile > Settings tab > expand Override Organisation Details, here populate the 'Portal URL' field with the portal URL this customer uses. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjliNzU4MGNmLThlMWEtNGYxZC05Nzg3LTgxMzZmNTIzZWJhNCJ9.t8L9IsjkYjqwYPlrmwsk2YMTimp6UPVHzl0K4qJkIQ8" class="fr-fic fr-fil fr-dib" width="961" style="width: 963px; height: 623.07px;" height="623"></p><p><strong><span style="font-size: 10pt;">Fig 9. Setting portal URL field against customer</span></strong></p><p><br></p><p>Once populated this field will be used to populate portal $-variables for this customer. This will override any organisation settings, that is, if a portal URL is set against the organisation that is working on the ticket, but the customer the ticket is for has a different portal URL set against them, the customer's portal URL will be used. </p><p><br></p><p><strong><span style="font-size: 14pt;">Restricting Portal Button access</span></strong></p><p>If you would like different organisations/customers/users to experience different functionality in the portal , this can be achieved by restricting which buttons they have access to in the portal. This is useful if you would only like certain customers to be able to log a particular ticket type in the portal, or would like only certain departments/users to have access to documents, invoices, knowledge base etc. </p><p><br></p><p>To do this head to Configuration > Self Service Portal > see the menu button section, edit the button you would like to restrict access to. Under the 'Visibility Restrictions' section you can add restrictions to this table, when adding to the table the entity you select will be allowed access to the button, anyone not in the table will not have access. Once saved you will be able to see the restriction set against the button. In <strong>Fig 10</strong> I have restricted the 'New Ticket' button so only users at Acorn Construction can see/use this button therefore area of the portal. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjQ5YjdkZDljLThmZWYtNGQ2ZS05MDRiLTY1NjVlN2M0ZjZlMyJ9.1AhCJ8GcfLTPYpqnLLpSLHKOt3uWI3Bhg2rihcaEWbk" class="fr-fic fr-fil fr-dib" width="1000" style="width: 1002px; height: 292.04px;" height="292"></p><p><strong><span style="font-size: 10pt;">Fig 10. Restricting visibility of portal button based on customer</span></strong></p><p><br></p><p>To see what users are under an organisation/department, head to Configuration > Organisation > Configure Organisations > Departments > edit a department > Members tab, here under the 'Users' table will be all the users under this department. </p><p><br></p><p><strong><em>Note: Restricting portal button access will apply to all your portals, not just the default portal.</em></strong></p><p><br></p><p><strong><span style="font-size: 14pt;">Restricting Portal FAQ list access</span></strong></p><p>FAQ list visibility in the portal can be restricted based on the portal the user if logged in to. That is an FAQ list can be visible in one portal, but not another. </p><p><br></p><p><strong><em>To be able to use this functionality you must be using multi-tenancy, with each portal associated to one of your organisations. </em></strong></p><p><br></p><p>To configure this you must first head to configuration > knowledge base, and enable the setting 'Enable the ability to restrict FAQ lists for Users on a Self Service Portal for different Organisations'. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImMyNzAwYTYzLWY3YzYtNGUwMC1iMDc5LTNlMzI1YWI1YWFmYyJ9.KlOUgcykFC2t4UNnLgrikhlHbNOpOApLTt0Wwc6BM6E" class="fr-fic fr-fil fr-dib" width="691" style="width: 693px; height: 289.918px;" height="290"></p><p><strong>Fig 11. Enable the ability to restrict FAQ lists for Users on a Self Service Portal for different Organisations</strong></p><p><br></p><p>Now against each of your portal applications you will need to set which organisation's branding they use. The portal applications can be found under configuration > integrations > HaloAPI > view applications, click into an application to edit it. Under the 'preferences' section of the portal application you can set which branding the portal uses. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjI1YmFjZmVhLTdiMTctNGQwYS1iMzNiLTgzNTY2ZGVjYzAxNiJ9.yDLTaHU7sJk8Mzn_s_nucUe3Nrqhe1OLMBv8O_9wMO0" class="fr-fic fr-fil fr-dib" width="590" style="width: 592px; height: 491.351px;" height="491"></p><p><strong><span style="font-size: 10pt;">Fig 12. Set branding against portal </span></strong></p><p><br></p><p>Now you can set FAQ list restrictions per organisation. Head to configuration > organisations > configure organisations > select an organisation > settings tab, here you will see a checkbox 'Users can see all available FAQ Lists', when this is unchecked you will be able to set the FAQ lists that users can see. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijg3YzAwMjM3LTVlNmQtNDBiMy1iOTI2LTZmOTdhNDc1MTljMiJ9.KbWb7BfWL-SYwtml2vAi3Po4WEduXX_cCATc4-Ddvvg" class="fr-fic fr-fil fr-dib" width="911" style="width: 913px; height: 640.883px;" height="641"></p><p><strong><span style="font-size: 10pt;">Fig 13. FAQ lists that Users can see</span></strong></p><p><br></p><p>The FAQ lists chosen here will be the FAQ lists that are visible in the portal that is set to use this organisation's branding. For example, if I set 'Portal for organisation 2' to use the branding of the 'HaloPSA local' organisation each user that logs into 'portal for organisation 2' will only see the FAQ lists set available under the 'HaloPSA' organisation. If the same user logged into another portal they would be able to see other/more FAQ lists. </p><p><br></p><p><strong><em>Note: FAQ Lists where "Show for everyone" is enabled ignore these restrictions.</em></strong></p><p><br></p><p id="isPasted"><strong><span style="font-size: 14pt;">Restricting Service access based on Portal</span></strong></p><p id="isPasted">The services that show/can be requested in the portal can be restricted based on the portal the user if logged in to. That is, a service can be visible in one portal, but not another. These restrictions are based on the organisation that is linked (branding being used) to the portal. </p><p><br></p><p id="isPasted"><strong><em>Note: To be able to use this functionality you must be using multi-tenancy, with each portal associated to one of your organisations. </em></strong></p><p id="isPasted"><br></p><p>To do this you will need to head to services > select a service > user access tab > add to the user access table. Here, set the entity to be 'Portal linked organisation', then choose which organisation's portal you would like to be able to access this service. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImRlYWNhMTBhLTY4YTAtNDBmYS1iYmQ4LWRjMmJjM2I4YTkxZiJ9.5nkw3igmw7r_LV1JcBTlJu2E_vIiczdydWHzbR1rzYk" class="fr-fic fr-fil fr-dib" width="579" height="345"></p><p data-pasted="true"><strong><span style="font-size: 10pt;">Fig 14. Restricting service access based on organisation portal</span></strong></p><p><br></p><p id="isPasted">The restrictions set here will apply to anyone logging into the portal that is set to use this organisation's branding. In the figure 14 example only users that are logging into the portal that is set to use the branding of 'International Halo' will be able to see/request this service. </p><p><br></p><p>Restrictions can also be set to be exclusive rather than inclusive using the 'Exclude this entity from this Service' checkbox. The same restriction can also be set per service category in the same way. For more information on setting restrictions against services check out our guide on <a data-fr-linked="true" href="https://usehalo.com/haloitsm/guides/1998/" id="isPasted" target="_blank" rel="noopener noreferrer"><strong>The Service Catalogue</strong></a>. </p><p><br></p><p data-pasted="true"><strong><span style="font-size: 14pt;">Enforcing Ticket Type restrictions based on Portal</span></strong></p><p>If multiple Portals are configured in your instance you can restrict which Tickets can be viewed in the My Tickets area based on which portal is being used. To do this you will need to enable "Enforce Organization Ticket Type restrictions" in Configuration > Self Service Portal. Once enabled, you can set your organisation restrictions in the Settings tab of each Organisation (Configuration > Organisation) by deselecting "Allow use of all Ticket Types" and using the drop-down to select which Tickets to allow.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjQ3YTc3MDA2LTMwZTktNDg4YS1hNGE4LTFkYmZmNmU0MGM4NiJ9.pvF3xueZ_KkSb9oxqCMNrSacnI8u0jvEGKoTUNsy57c" class="fr-fic fr-fil fr-dib" width="1264" style="width: 1266px; height: 333.789px;" height="334"></p><p data-pasted="true"><strong><span style="font-size: 10pt;">Fig 15. Organisation's allowed Ticket Types</span></strong></p><p><br></p><p><br></p><p data-pasted="true"><strong><span style="font-size: 14pt;">Portal Selection when impersonating a User</span></strong></p><p data-pasted="true">To choose which Portal to view when impersonating a User, head to Configuration > Advanced Settings, and enable "Allow portal selection when impersonating a User". With this setting enabled, a popup will show when impersonating a User allowing you to select which portal to view.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjRlOTkxM2QzLTE1MTctNDdlZi1hMWJjLWU4NjkzNDZmODUxYSJ9.JmCilsIuNzM-u2Qtn1E_oVt8q8QOVC59I83_2MVrnC0" class="fr-fic fr-fil fr-dib" width="835" style="width: 837px; height: 432.898px;" height="433"></p><p><strong><span style="font-size: 10pt;">Fig 16. Selecting an organisation portal </span></strong></p>
