The visibility question every support tool fumbles
Who should see which incidents? Most tools pick one of two bad answers:
- Everyone sees everything. Simple, until an HR incident about a salary dispute is readable by the whole IT team. Confidentiality dies, and so does the queue - every agent scrolls past everyone else's work.
- You only see what is assigned to you. Tidy, until a colleague is on holiday and their incidents are invisible to the rest of the team. Unassigned work sits in a void nobody is allowed to look into.
Both answers fail because neither matches how teams actually divide work.
How visibility works in NSupport Platform
Incidents carry a category - the department or topic they belong to: hardware, HR, facilities, billing, whatever your workspace defines. Visibility follows role:
- Members see only the incidents they reported themselves. Your request is your business; your colleague's is not.
- Agents see the union of three things: incidents assigned to them, incidents they reported, and every incident in a category they cover.
- Admins and Owners see everything in the workspace - someone has to hold the full picture.
The middle rule is the one that matters. An agent's view is defined by coverage, not by a personal queue. Admins assign each agent the categories they are responsible for, and the incident list, the detail pages, and even the AI assistant's lookups all follow the same rule, enforced in the data layer.
"Work the departments you own, cover for a colleague"
Category coverage maps to how real teams describe their own work:
- The hardware specialist covers Hardware and sees every hardware incident - assigned, unassigned, or sitting with the colleague who just went on leave. Covering is built in, not a permissions request.
- The HR generalist covers HR and never sees IT incidents - and crucially, the IT team never sees HR's. Sensitive categories stay inside the circle that handles them.
- New unassigned incidents are immediately visible to every agent covering that category. Triage happens because the right people can already see the work, not because a dispatcher remembered to route it.
And the two personal rules keep edge cases sane: if something was assigned to you from outside your usual categories, you can see it; if you reported an incident yourself, you can follow it like any member would.
Least privilege without the lockout
The principle underneath is least privilege - nobody holds access they do not need. But least privilege usually arrives as friction: locked doors, access tickets, waiting. Category coverage delivers it as a natural shape instead. Each agent's view is exactly their job: the departments they own, the work on their plate, the things they personally raised.
When responsibilities shift, an admin updates the agent's categories and visibility follows instantly. No share links, no per-incident permissions, no everyone-sees-everything fallback. Access that mirrors the org chart, kept current in one screen.