Case Permissions

The Permissions window answers two questions: who can see the case and why, and who can trigger which event on it. Open it from the case detail via More → Permissions. The window is read-only and you cannot change permissions in it. Permissions are set in the template, in roles and in the organizational structure.

Case visibility

The Case visibility tab opens first. Each row is one reason why one user can see the case. This means the same user often appears more than once.

No.ElementPurpose
1Case visibilitySwitches to this tab.
2EventsSwitches to the events tab, see below.
3Display nameThe user who can see the case. Type part of a name to narrow down the list. In the image, the list is narrowed down to Klára.
4TypeWhy the user can see the case, see the table below. Filter by selecting one or more types.
5NameThe specific source of the permission: the name of the task, role or organizational unit.
6DetailEye icon. On a task row, it opens the task detail. On a role or organizational unit row, an administrator can use it to go to the role or unit settings. If there is nothing to open, the icon is inactive.
TypeMeaning
Case ownerThe user owns the case.
Task solverThe user is solving or has solved a task of the case. The Name column shows the task name.
Task supervisorThe user is the supervisor of a task of the case.
Visibility from task to pullThe user can take over a task of the case.
Visibility for roleThe user has a role to which the template gives visibility of its cases. The Name column shows the role.
Visibility for org. unitThe user belongs to an organizational unit that has visibility of the template's cases.
Static rightA right assigned directly to the case.
Dynamic rightA right that the template assigns to the case.

The list is often long, because all administrators and users with roles that have company-wide visibility can also see the case. If you are looking for a specific person, type their name into the Display name filter.

Why a colleague cannot see the case
If a colleague is not in the list, they cannot see the case. You can give them access to the case by handing over a task to them, or ask the template administrator for a role with visibility of this type of case.

Events

The Events tab shows who can trigger which event on the case. You trigger events with the Event button in the case detail, see the article Events on a Case.

ColumnPurpose
Display nameThe user who can trigger the event.
Task nameThe name of the event as it appears in the Event window.
TaskThe eye icon opens the event detail.

The image shows that Klára can trigger four events on her purchase order, for example Copy the Purchase Order or Print to PDF.

Administrators see additional columns in this tab that show why the user is allowed to trigger the event:

ColumnPurpose
Relation to reference personHow the event solver is derived from the reference person: Reference person only, Direct superior, All superiors, Direct subordinates, All subordinates, Colleagues of reference person, or no relation.
Reference personThe person from whom the solver is derived, typically the case owner.
RoleThe role the event solver must have.
Org. unitThe organizational unit the event solver must belong to.

Like any list, both tabs can be exported, for example when you need to document who had access to the case.

Related: Case Detail, Events on a Case.

Case Events

Subscribing to an overview by email
Syca (opens in a new tab)

Powered by HelpDocs (opens in a new tab)