Skip to content
English
Q7LEADER
  • There are no suggestions because the search field is empty.

All - Guide to Objectives & Conversations Notifications

This guide explains how notifications work for Objectives and Conversations modules. You’ll learn when and how notifications are triggered and who receives them.

Key Features:

  • Notifications when New/Draft
  • Notifications when Pending
  • Notifications for comment added (Objectives Only)

Notifications now follow the submission flow. All modules using this flow (such as Objectives and Conversations) work under the same principles.

Note: This submission and notification workflow functions efficiently only when team members have user accounts and assigned managers.

  • Both member and manager have users: Submission works normally → double submission possible.

  • Only one has a user: The one with a user can submit normally, but double submission is not possible, and they cannot submit on behalf of the other.

  • Neither has a user: Digital submission cannot function.

  • Member has no manager: Member can submit normally, but double submission is not possible.

A conversation can only be created when both a team member and a manager are assigned. Each conversation is always linked to exactly two participants.

An objective, however, can be created even if two users are not assigned. If a team member creates an objective without having a manager assigned, double submission is not possible.

Once an objective has been submitted by a manager, that manager will continue to receive notifications for the objective even if the manager assignment later changes. This is because notifications remain linked to the manager who submitted it.

To redirect notifications to a new manager, HR must reset the submission, after which the team member and the new manager must resubmit the objective.

When the State is: New and Draft

Action is:

-Save Draft

  • Sends nothing.

-Save

  • If the Author is the Team Member → Manager gets notified.
  • If the Author is the Manager → Team Member gets notified.
  • If the Author is Other → Team Member and Manager get notified.

-Submit

  • Submitted by Team Member → Manager gets notified.
  • Submitted by Manager → Team Member gets notified.

When the State is Pending and Neither participant has submitted

Action is:

-Save / Edit + Save → Sends nothing.

-Submit / Edit + Submit

  • Submitted by Team Member → Manager gets notified.
  • Submitted by Manager → Team Member gets notified.

-Submission Reset → Sends nothing.

When the State is Pending and only One participant has submitted

Action is:

-Save

  • Sends nothing.

-Edit + Save

  • If ManagerSubmit = True and edited by Team Member or Other → Manager gets notified., submission resets (ManagerSubmit=False).
  • If MemberSubmit = True and edited by Manager or Other → Team Member gets notified., submission resets (MemberSubmit=False).

-Edit + Submit

  • If ManagerSubmit = True and submitted by Team Member → Manager gets notified., submission resets.
  • If MemberSubmit = True and submitted by Manager → Team Member gets notified., submission resets.

-Submit

  • If ManagerSubmit = True and submitted by Team Member → Manager gets notified.
  • If MemberSubmit = True and submitted by Manager → Team Member gets notified.

-Submission Reset (by HR)

  • If MemberSubmit = True → Team Member gets notified.
  • If ManagerSubmit = True → Manager gets notified.

When the State is Signed Off and Both parties have submitted

Action is:

-Submission Reset

  • Team Member and Manager get notified.

Anytime (Objectives Only)

Action is:

-Comment

  • Author = Team Member → Manager gets notified.
  • Author = Manager → Team Member gets notified.
  • Author = Other → Team Member and Manager get notified.