Knowledge Base

My team's worklist

Your own worklist - the bell in the top right - shows what is waiting for you. This page shows what is waiting for the people who report to you.

Rebuilt excerpt of the view: /settings/notifications/team

Who can see this page

Only a supervisor, and only for their own reporting line.

There is no separate permission anybody could grant for it. What counts is solely who is entered as supervisor in the employee record: you see the worklists of exactly those people whose record names you in that field. If nobody reports to you, the page says so in one sentence and shows nothing.

The difference from a permission is not a formality. A permission would be true for everybody holding it and would say nothing about whose team is meant. The supervisor relation gives a different answer for every person, and it cannot be granted by accident.

Every visit is recorded

A worklist entry reveals who asked for what. Every visit to this page is therefore written to the audit trail - not just a change, but the looking itself.

That is deliberate, and the page says so before you look. Anyone who is given a view into other people's requests should know that the view is traceable; and anyone who files a request should be able to rely on it.

What a row says

  • The subject of the process
  • The process kind - for example "Absence request filed"
  • Sits with - whose worklist the process is on
  • Arrived - when it appeared there
  • Open process - the jump to the source

If the process reached the list through escalation - because the person actually responsible had not decided for too long - the row says so as well.

What you cannot do here

Decide. This page only shows. A process is settled by the person it sits with, or through the process itself - that is what "Open process" is for, and the rules of the respective area apply there. A "decide on somebody's behalf" button here would be a second approval path, and there is not meant to be one.

What applies when you are being stood in for

A stand-in does not inherit this view. Whoever is entered as your absence deputy receives the affected processes on their own worklist while you are away, and can decide them there. That needs no view into your team list - and such a view would reach further than the deputising does: it would cover every entry of the team, including on the days you are at your desk.

If somebody is to see the team list permanently, that person is entered as a supervisor. That is a decision somebody makes on purpose, not a side effect of a deputy field.

What applies when the reporting line changes

At once, and in both directions. The page asks on every visit who reports to whom today:

  • If a person moves out of your team, their entries disappear from your view immediately - the old ones too.
  • If you take over a team, you see its open entries immediately, including those that arrived before your time.

The second case is the price of the first, and it is the smaller one: those are exactly the processes you are now answerable for. The first case is the more important one - a former manager should not keep seeing who in their old team asked for what.

Searching and filtering

Above the list there is a Process kind field that narrows to a single kind. Your selection lives in the browser's address bar, so you can keep the view as a bookmark. Anybody you send that link to, however, sees their own team with the same selection, not yours.