You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a default setting for an account to ONLY receive notification on NEW reports (and not changes to existing ones)
Motivation and context
We have clients, who uses a different entity (KL) to recieve and validate incoming reports. KL is handling a large amount of clients, hence, they have many sýstems to handle. For each system, they have personal accounts as well as a common group account, to monitor incoming reports from all systems (to ensure, that no reports are 'drowned' in the personal account mailboxes). This account is not used to do any case handling.
We are aware of, that notifications can be disabled on each case seperately, but this requires login to each case to set this value, so to easen the burden, a global setting for the account could come in handy. KL informed us, that the other systems, that they used has this feature
The text was updated successfully, but these errors were encountered:
Proposal
Create a default setting for an account to ONLY receive notification on NEW reports (and not changes to existing ones)
Motivation and context
We have clients, who uses a different entity (KL) to recieve and validate incoming reports. KL is handling a large amount of clients, hence, they have many sýstems to handle. For each system, they have personal accounts as well as a common group account, to monitor incoming reports from all systems (to ensure, that no reports are 'drowned' in the personal account mailboxes). This account is not used to do any case handling.
We are aware of, that notifications can be disabled on each case seperately, but this requires login to each case to set this value, so to easen the burden, a global setting for the account could come in handy. KL informed us, that the other systems, that they used has this feature
The text was updated successfully, but these errors were encountered: