How Public and Private Solutions work
ServiceDesk Plus MSP allows you to
publish knowledge base solutions as either public (available for all requesters
and technicians) or private (accessible only by technicians).
To make a solution public, while
adding/editing the solution select the checkbox "Publish this solution in Self-Service Portal also". This will make the solution
available to the requesters also. If you do not wish the requester to view any
of the solutions, then just leave this check box disabled.
This feature has been implemented as
per the industry standards where some of the solutions entered would not be
relevant to the requester and hence can be made as private articles.
New to ADSelfService Plus?
Related Articles
How to Hide the Solutions for Requesters
Logon to the application as administrator. To Hide the Solutions In the Home tab, click on the Customize menu as shown in the below tab, and select on the Requester Home Page, In the theme tab , select on the edit button on the theme in which you ...
Script to Mark conversations with Requester email not in from, to or cc as Private
Requirement : Any conversation in which the requester's email is not present in from, to or cc must be marked as a private conversation ( Requester of the request will not be able to view this reply ) If an external user replies to a request, the ...
Change Conversation as "Private" when the external user replies to the Request
Recently one of our customers had the requirement to change the conversation to "Private" when the external user replies to the request. Customer's workflow: The request is created by a user who is inside the application. Now the admin is forwarding ...
Auto suggest solutions to technicians
Use Case When a request is created, solutions can be auto suggested to technicians under Resolution Tab with a bulb icon. Based on the subject keywords the available solutions will be suggested to the technician which will help them narrow down the ...
Live Chat Doesn't work Outside the server
Issue: Live chat function works on the MSP server i.e. works only when tried on localhost, however does not work outside it. Same will be the case with Bell notification and Request collaboration features. Cause: This happens mostly on HTTPS where ...