Please share with the community what you think needs improvement with SysAid.
What are its weaknesses? What would you like to see changed in a future version?
The Knowledge Base would be another area where I would look for growth in SysAid. It is very much a text-based article system, or you can do attachments. But I'd like to see it grow so that it is more graphical and has some additional tracking features. The Knowledge Base is a simple text editor. I'd like to have more formatting and be able to use more visual elements within the tool. One of the features that I'm hoping comes at some point is that currently you can only have one Knowledge Base instance within it. For me, it would be beneficial to have multiple instances for different purposes. I'd like to have a completely separate one for customers and the only way I can achieve that right now, where I can tag articles to only be viewed by customers, would be if I use its portal function. The portal function is not a function, at this time, that my organization would have any need to turn on. Because of that, I'm limited. I can't directly expose articles to customers. I'd like to see a little bit more development in that area where you're able to have segmentation of knowledge. The other aspect that I'd like to see is that, in the Knowledge Base and in the CMDB, I can't run reports into those entities. I can do it from the incidents and requests — and problem management, but we don't use that. So for the Knowledge Base and CMDB, I have to go into the dashboard for each one of those and use filters to get to the information that I want, and then I can export it. A nice feature and growth opportunity for SysAid would be to develop the reporting tool and link reporting capabilities to all the aspects within the total solution.
We would like them to approve the security functionalities, e.g., management security features. Currently, the way society is set up in our agency is that we only have two roles. There is either end user roles, where an end user can submit requests for help and incidents, then they can see the status of what is going on with them. We also have what are called system administrators. These are people who are providing the support, but there isn't any role based security. For example, if I could divvy up the security, I would like a staff role and a manager role, so a manager can look at all the different tickets that their staff has submitted and what the status is, as end users. For support people, I would like them to be able to figure out a way to separate out the support that is provided by the IT staff versus the facility staff, HR people, or finance people. Right now, we only have two roles: Either you are an end user, but then you can also be an office admin. This means the facilities people can see every ticket that is in the support queue, which is not great. This is an area where we would like much clearer, broader role based security from SysAid.
The module of Knowledgebase should be definitely improved in the consideration of the impossibility of referring an article to a ticket. Also, the vendor should consider improving the obsolete admin portal.