Skip to main content

Relationships

A relationship is a kind of relationship between a participant and the staff who look after them, such as a key worker. Each kind has default assignees, who must be staff. A participant is assigned a user relationship per kind, naming their own assignee.

Relationships are how a journey reaches the right staff without naming anyone:

  • createUserEmailMessage and createUserSmsMessage with a kind in recipients, and createUserTask with a kind in assignees, go to the participant's assignee of that kind, or, when they have none, to the kind's default assignees. A kind that reaches nobody sends nothing, and the journey warns before it is published.
  • relationships.<relationship> exists in a condition reads the kinds assigned to the participant; a kind's default assignees don't count.

Kinds in the shared library are readable by every tenant and editable only by the DEFAULT tenant; a tenant wanting its own default assignees for a library kind adds its own with the same code.