Support & frequently asked questions

My main argument would be that I can place the panel in the side panel, which gives me an instant view—even when working from a selection. But there is also an other aspect. In my personal experience, support agents who spend their entire day in the request module tend to stay there. They typically avoid navigating away unless absolutely necessary. This isn’t just specific to SuperOffice—it's something I’ve observed across some support organizations. There’s a significant difference in user experience between switching tabs within the same entity and navigating away to the company card. One key aspect is the perceived loading time. Users generally prefer not to visually reload the entire screen and then return if they could get the informaiton with in the support request. When navigating to the company card, users expect a longer loading time. But when switching tabs within the request screen, they expect a seamless, instant transition.  Other teams who work across different parts of SuperOffice might be more open to navigating between modules. But for support teams, the request screen is their primary workspace, and wish to have the informatiuon they need straigt there. 

In general, working with project members can be a bit tricky because they are stored in a separate table in the database that sits between the project and the person. This setup allows for a  many-to-many relationship : One person can be a member of multiple projects, and one project can have multiple members. The downside of this structure is that you  can’t see projects when searching for a person , and you  can’t see people when searching for a project . However, there’s a workaround using the old  Service search tables , which allows you to search directly in the  projectmember  table. This lets you display the full list of project members. If you have a Service license, you can use the following URL to go straight to a project member search. Just replace  XXXX  with your customer ID: https://online.superoffice.com/CustXXXX/CS/scripts/ticket.fcgi?_sf=0&action=searchTable&table=projectmember This method won’t allow you to see all projects that don’t have any members, but it does provide a simple overview of all members across all projects.

Thanks, appreciate your effort.